CVE-2024-53055: wifi: iwlwifi: mvm: fix 6 GHz scan construction
Noroxi assessment
Priority: Monitor (action score 22/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.25% (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 2ac15e5a8f42fed5d90ed9e1197600913678c50f, 2ccd5badadab2d586e91546bf5af3deda07fef1f, 7245012f0f496162dd95d888ed2ceb5a35170f1a; azl3 kernel 6.6.57.1-7 on Azure Linux 3.0 6.6.64.2-1; azl3 kernel 6.6.64.2-1 on Azure Linux 3.0 6.6.64.2-1.
Low priority for now. Upgrade to Linux Linux 2ac15e5a8f42fed5d90ed9e1197600913678c50f, 2ccd5badadab2d586e91546bf5af3deda07fef1f, 7245012f0f496162dd95d888ed2ceb5a35170f1a; azl3 kernel 6.6.57.1-7 on Azure Linux 3.0 6.6.64.2-1; azl3 kernel 6.6.64.2-1 on Azure Linux 3.0 6.6.64.2-1 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: iwlwifi: mvm: fix 6 GHz scan construction If more than 255 colocated APs exist for the set of all APs found during 2.4/5 GHz scanning, then the 6 GHz scan construction will loop forever since the loop variable has type u8, which can never reach the number found when that's bigger than 255, and is stored in a u32 variable. Also move it into the loops to have a smaller scope. Using a u32 there is fine, we limit the number of APs in the scan list and each has a limit on the number of RNR entries due to the frame size. With a limit of 1000 scan results, a frame size upper bound of 4096 (really it's more like ~2300) and a TBTT entry size of at least 11, we get an upper bound for the number of ~372k, well in the bounds of a u32.
- Published
- Nov 19, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 17th percentile
- CWE
- CWE-835
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
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
- 5.11affected
- eae94cf82d7456b57fa9fd55c1edb8a726dcc19c and later · before 2ac15e5a8f42fed5d90ed9e1197600913678c50faffected · git
- eae94cf82d7456b57fa9fd55c1edb8a726dcc19c and later · before cde8a7eb5c6762264ff0f4433358e0a0d250c875affected · git
- eae94cf82d7456b57fa9fd55c1edb8a726dcc19c and later · before fc621e7a043de346c33bd7ae7e2e0c651d6152efaffected · git
- eae94cf82d7456b57fa9fd55c1edb8a726dcc19c and later · before 2ccd5badadab2d586e91546bf5af3deda07fef1faffected · git
- eae94cf82d7456b57fa9fd55c1edb8a726dcc19c and later · before 7245012f0f496162dd95d888ed2ceb5a35170f1aaffected · git
- before 5.11not affected · semver
- 5.15.171 and later · up to and including 5.15.*not affected · semver
- 6.1.116 and later · up to and including 6.1.*not affected · semver
- 6.6.60 and later · up to and including 6.6.*not affected · semver
Affected versions · NVD (5)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.11 and later · before 5.15.171
- linux linux kernel5.16 and later · before 6.1.116
- linux linux kernel6.2 and later · before 6.6.60
- linux linux kernel6.7 and later · before 6.11.7
- linux linux kernel6.12
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.119-1 | 6.1.119-1 |
| Debian:13 | linux | before 6.11.7-1 | 6.11.7-1 |
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-53052Nov 19, 2024 · io_uring/rw: fix missing NOWAIT check for O_DIRECT start write17Monitor
- ← EarlierCVE-2024-53053Nov 19, 2024 · scsi: ufs: core: Fix another deadlock during RTC update22Monitor
- Later →CVE-2024-53058Nov 19, 2024 · net: stmmac: TSO: Fix unbalanced DMA map/unmap for non-paged SKB data22Monitor
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 | 2ac15e5a8f42fed5d90ed9e1197600913678c50f | Vendor (CNA) |
| Linux Linux | 2ccd5badadab2d586e91546bf5af3deda07fef1f | Vendor (CNA) |
| Linux Linux | 7245012f0f496162dd95d888ed2ceb5a35170f1a | Vendor (CNA) |
| Linux Linux | cde8a7eb5c6762264ff0f4433358e0a0d250c875 | Vendor (CNA) |
| Linux Linux | fc621e7a043de346c33bd7ae7e2e0c651d6152ef | Vendor (CNA) |
| azl3 kernel 6.6.57.1-7 on Azure Linux 3.0 | 6.6.64.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 kernel 6.6.64.2-1 on Azure Linux 3.0 | 6.6.64.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.167.1-2 on CBL Mariner 2.0 | 5.15.173.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.167.1-2 on CBL-Mariner 2.0 | 5.15.173.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.173.1-1 on CBL Mariner 2.0 | 5.15.173.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.119-1 · Debian:12 | 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-31448519 days apartext4: avoid infinite loops caused by residual data37Monitor
- CVE-2026-23451500 days apartbonding: prevent potential infinite loop in bond_header_parse()30Monitor
- CVE-2026-31552521 days apartwifi: wlcore: Return -ENOMEM instead of -EAGAIN if there is not enough headroom30Monitor
- CVE-2024-27032202 days apartf2fs: fix to avoid potential panic during recovery25Monitor
- CVE-2022-48635205 days apartfsdax: Fix infinite loop in dax_iomap_rw()24Monitor
- CVE-2024-502721 days apartfilemap: Fix bounds checking in filemap_read()22Monitor
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
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-835 · Loop with Unreachable Exit Condition ('Infinite Loop')CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 (5 more)Show less
- git.kernel.org/stable/c/2ccd5badadab2d586e91546bf5af3deda07fef1f
- git.kernel.org/stable/c/7245012f0f496162dd95d888ed2ceb5a35170f1a
- git.kernel.org/stable/c/cde8a7eb5c6762264ff0f4433358e0a0d250c875
- git.kernel.org/stable/c/fc621e7a043de346c33bd7ae7e2e0c651d6152ef
- lists.debian.org/debian-lts-announce/2025/01/msg00001.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.