CVE-2024-57990: wifi: mt76: mt7925: fix off by one in mt7925_load_clc()
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 08fa656c91fd5fdf47ba393795b9c0d1e97539ed, 2d1628d32300e4f67ac0b7409cbfa7b912a8fe9d, 6.11.
Low priority for now. Upgrade to Linux Linux 08fa656c91fd5fdf47ba393795b9c0d1e97539ed, 2d1628d32300e4f67ac0b7409cbfa7b912a8fe9d, 6.11 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: mt7925: fix off by one in mt7925_load_clc() This comparison should be >= instead of > to prevent an out of bounds read and write.
- Published
- Feb 26, 2025
- Updated
- Aug 5, 2026
- EPSS
- 0.2% · 14th percentile
- CWE
- CWE-193
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.8
- CNA · Linux
- 7.8
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- fb60020cb5b3ea4715e538c77e745c16516c5656, ba09084d81c6480bd02fd74052045e533a5e8469, 6.12affected
- 9679ca7326e52282cc923c4d71d81c999cb6cd55 and later · before d03b8fe1b518fc2ea2d82588e905f56d80cd64b2affected · git
- 9679ca7326e52282cc923c4d71d81c999cb6cd55 and later · before 2d1628d32300e4f67ac0b7409cbfa7b912a8fe9daffected · git
- 9679ca7326e52282cc923c4d71d81c999cb6cd55 and later · before 08fa656c91fd5fdf47ba393795b9c0d1e97539edaffected · git
- 6.10.13 and later · before 6.11affected · semver
- 6.11.2 and later · before 6.12affected · semver
- before 6.12not affected · semver
- 6.12.13 and later · up to and including 6.12.*not affected · semver
- 6.13.2 and later · up to and including 6.13.*not affected · semver
- 6.14 and laternot affected · original_commit_for_fix
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.10.13 and later · before 6.11
- linux linux kernel6.11.2 and later · before 6.12.13
- linux linux kernel6.13 and later · before 6.13.2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | linux | before 6.12.13-1 | 6.12.13-1 |
| Red Hat:rhel_eus:9.6::appstream | kernel-64k-debug-debuginfo | before 0:5.14.0-570.146.1.el9_6 | 0:5.14.0-570.146.1.el9_6 |
| Red Hat:rhel_eus:9.6::appstream | kernel-64k-debug-devel | before 0:5.14.0-570.146.1.el9_6 | 0:5.14.0-570.146.1.el9_6 |
| Red Hat:rhel_eus:9.6::appstream | kernel-64k-debug-devel-matched | before 0:5.14.0-570.146.1.el9_6 | 0:5.14.0-570.146.1.el9_6 |
| Red Hat:rhel_eus:9.6::appstream | kernel-64k-debuginfo | before 0:5.14.0-570.146.1.el9_6 | 0:5.14.0-570.146.1.el9_6 |
| Red Hat:rhel_eus:9.6::appstream | kernel-64k-devel | before 0:5.14.0-570.146.1.el9_6 | 0:5.14.0-570.146.1.el9_6 |
| Red Hat:rhel_eus:9.6::appstream | kernel-64k-devel-matched | before 0:5.14.0-570.146.1.el9_6 | 0:5.14.0-570.146.1.el9_6 |
| Red Hat:rhel_eus:9.6::appstream | kernel-debug-debuginfo | before 0:5.14.0-570.146.1.el9_6 | 0:5.14.0-570.146.1.el9_6 |
| Red Hat:rhel_eus:9.6::appstream | kernel-debug-devel | before 0:5.14.0-570.146.1.el9_6 | 0:5.14.0-570.146.1.el9_6 |
| Red Hat:rhel_eus:9.6::appstream | kernel-debug-devel-matched | before 0:5.14.0-570.146.1.el9_6 | 0:5.14.0-570.146.1.el9_6 |
| Red Hat:rhel_eus:9.6::appstream | kernel-debuginfo | before 0:5.14.0-570.146.1.el9_6 | 0:5.14.0-570.146.1.el9_6 |
| Red Hat:rhel_eus:9.6::appstream | kernel-debuginfo-common-aarch64 | before 0:5.14.0-570.146.1.el9_6 | 0:5.14.0-570.146.1.el9_6 |
| Red Hat:rhel_eus:9.6::appstream | kernel-debuginfo-common-ppc64le | before 0:5.14.0-570.146.1.el9_6 | 0:5.14.0-570.146.1.el9_6 |
| Red Hat:rhel_eus:9.6::appstream | kernel-debuginfo-common-s390x | before 0:5.14.0-570.146.1.el9_6 | 0:5.14.0-570.146.1.el9_6 |
| Red Hat:rhel_eus:9.6::appstream | kernel-debuginfo-common-x86_64 | before 0:5.14.0-570.146.1.el9_6 | 0:5.14.0-570.146.1.el9_6 |
| Red Hat:rhel_eus:9.6::appstream | kernel-devel | before 0:5.14.0-570.146.1.el9_6 | 0:5.14.0-570.146.1.el9_6 |
| Red Hat:rhel_eus:9.6::appstream | kernel-devel-matched | before 0:5.14.0-570.146.1.el9_6 | 0:5.14.0-570.146.1.el9_6 |
| Red Hat:rhel_eus:9.6::appstream | kernel-doc | before 0:5.14.0-570.146.1.el9_6 | 0:5.14.0-570.146.1.el9_6 |
| Red Hat:rhel_eus:9.6::appstream | kernel-rt-64k-debug-debuginfo | before 0:5.14.0-570.146.1.el9_6 | 0:5.14.0-570.146.1.el9_6 |
| Red Hat:rhel_eus:9.6::appstream | kernel-rt-64k-debuginfo | before 0:5.14.0-570.146.1.el9_6 | 0:5.14.0-570.146.1.el9_6 |
| Red Hat:rhel_eus:9.6::appstream | kernel-rt-debug-debuginfo | before 0:5.14.0-570.146.1.el9_6 | 0:5.14.0-570.146.1.el9_6 |
| Red Hat:rhel_eus:9.6::appstream | kernel-rt-debuginfo | before 0:5.14.0-570.146.1.el9_6 | 0:5.14.0-570.146.1.el9_6 |
| Red Hat:rhel_eus:9.6::appstream | kernel-tools-debuginfo | before 0:5.14.0-570.146.1.el9_6 | 0:5.14.0-570.146.1.el9_6 |
| Red Hat:rhel_eus:9.6::appstream | kernel-zfcpdump-debuginfo | before 0:5.14.0-570.146.1.el9_6 | 0:5.14.0-570.146.1.el9_6 |
+68
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-57988Feb 26, 2025 · Bluetooth: btbcm: Fix NULL deref in btbcm_get_board_name()22Monitor
- ← EarlierCVE-2024-57989Feb 26, 2025 · wifi: mt76: mt7925: fix NULL deref check in mt7925_change_vif_links22Monitor
- Later →CVE-2024-57991Feb 26, 2025 · wifi: rtw89: chan: fix soft lockup in rtw89_entity_recalc_mgnt_roles()22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 08fa656c91fd5fdf47ba393795b9c0d1e97539ed | Vendor (CNA) |
| Linux Linux | 2d1628d32300e4f67ac0b7409cbfa7b912a8fe9d | Vendor (CNA) |
| Linux Linux | 6.11 | Vendor (CNA) |
| Linux Linux | 6.12 | Vendor (CNA) |
| Linux Linux | d03b8fe1b518fc2ea2d82588e905f56d80cd64b2 | Vendor (CNA) |
| debian:linux | 6.12.13-1 · Debian:13 | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-570.146.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-570.146.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-570.146.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-570.146.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-570.146.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-570.146.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-570.146.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-570.146.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:5.14.0-570.146.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:5.14.0-570.146.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:5.14.0-570.146.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-ppc64le | 0:5.14.0-570.146.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-53088483 days apartnet: bcmgenet: fix off-by-one in bcmgenet_put_txcb39Monitor
- CVE-2026-53309485 days apartocfs2/dlm: fix off-by-one in dlm_match_regions() region comparison39Monitor
- CVE-2026-64047508 days apartnet: tls: fix off-by-one in sg_chain entry count for wrapped sk_msg ring39Monitor
- CVE-2024-47682128 days apartscsi: sd: Fix off-by-one error in sd_read_block_characteristics()31Monitor
- CVE-2024-49880128 days apartext4: fix off by one issue in alloc_flex_gd()31Monitor
- CVE-2024-46852152 days apartdma-buf: heaps: Fix off-by-one in CMA heap fault handler31Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-193 · Off-by-one ErrorCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.