CVE-2024-50272: filemap: Fix bounds checking in filemap_read()
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.27% (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 26530b757c81f1389fb33ae0357500150933161b, 3.17, 4.8; 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 26530b757c81f1389fb33ae0357500150933161b, 3.17, 4.8; 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: filemap: Fix bounds checking in filemap_read() If the caller supplies an iocb->ki_pos value that is close to the filesystem upper limit, and an iterator with a count that causes us to overflow that limit, then filemap_read() enters an infinite loop. This behaviour was discovered when testing xfstests generic/525 with the "localio" optimisation for loopback NFS mounts.
- Published
- Nov 18, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 19th 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%
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
- 272830350bb1bb5bb39395966ea63b9864b135d1, fbc7b803831e5c8a42c1f3427a17e55a814d6b3c, 3d549dcfbbb0ecdaa571431a27ee5da9f2466716, 4.9affected
- c2a9737f45e27d8263ff9643f994bda9bac0b944 and later · before 6cc52df69e8464811f9f6fc12f7aaa78451eb0b8affected · git
- c2a9737f45e27d8263ff9643f994bda9bac0b944 and later · before 26530b757c81f1389fb33ae0357500150933161baffected · git
- c2a9737f45e27d8263ff9643f994bda9bac0b944 and later · before a2746ab3bbc9c6408da5cd072653ec8c24749235affected · git
- c2a9737f45e27d8263ff9643f994bda9bac0b944 and later · before 6450e73f4c86d481ac2e22e1bc848d346e140826affected · git
- c2a9737f45e27d8263ff9643f994bda9bac0b944 and later · before ace149e0830c380ddfce7e466fe860ca502fe4eeaffected · git
- 3.16.40 and later · before 3.17affected · semver
- 4.7.10 and later · before 4.8affected · semver
- 4.8.4 and later · before 4.9affected · semver
- before 4.9not affected · semver
Affected versions · NVD (7)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel3.16.40 and later · before 3.17
- linux linux kernel4.7.10 and later · before 4.8
- linux linux kernel4.8.4 and later · before 4.9
- linux linux kernel4.9 and later · before 6.1.117
- linux linux kernel6.2 and later · before 6.6.61
- linux linux kernel6.7 and later · before 6.11.8
- 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.9-1 | 6.11.9-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-50270Nov 18, 2024 · mm/damon/core: avoid overflow in damon_feed_loop_next_input()22Monitor
- ← EarlierCVE-2024-50271Nov 18, 2024 · signal: restore the override_rlimit logic22Monitor
- Later →CVE-2024-50273Nov 18, 2024 · btrfs: reinitialize delayed ref list after deleting it from the list22Monitor
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 | 26530b757c81f1389fb33ae0357500150933161b | Vendor (CNA) |
| Linux Linux | 3.17 | Vendor (CNA) |
| Linux Linux | 4.8 | Vendor (CNA) |
| Linux Linux | 4.9 | Vendor (CNA) |
| Linux Linux | 6450e73f4c86d481ac2e22e1bc848d346e140826 | Vendor (CNA) |
| Linux Linux | 6cc52df69e8464811f9f6fc12f7aaa78451eb0b8 | Vendor (CNA) |
| Linux Linux | a2746ab3bbc9c6408da5cd072653ec8c24749235 | Vendor (CNA) |
| Linux Linux | ace149e0830c380ddfce7e466fe860ca502fe4ee | 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.180.1-1 on CBL Mariner 2.0 | CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.180.1-1 on CBL-Mariner 2.0 | 5.15.182.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-31448520 days apartext4: avoid infinite loops caused by residual data37Monitor
- CVE-2026-23451501 days apartbonding: prevent potential infinite loop in bond_header_parse()30Monitor
- CVE-2026-31552522 days apartwifi: wlcore: Return -ENOMEM instead of -EAGAIN if there is not enough headroom30Monitor
- CVE-2024-27032201 days apartf2fs: fix to avoid potential panic during recovery25Monitor
- CVE-2022-48635204 days apartfsdax: Fix infinite loop in dax_iomap_rw()24Monitor
- CVE-2024-530551 days apartwifi: iwlwifi: mvm: fix 6 GHz scan construction22Monitor
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/6450e73f4c86d481ac2e22e1bc848d346e140826
- git.kernel.org/stable/c/6cc52df69e8464811f9f6fc12f7aaa78451eb0b8
- git.kernel.org/stable/c/a2746ab3bbc9c6408da5cd072653ec8c24749235
- git.kernel.org/stable/c/ace149e0830c380ddfce7e466fe860ca502fe4ee
- lists.debian.org/debian-lts-announce/2025/01/msg00001.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.