CVE-2026-74349: ocfs2: reject FITRIM ranges shorter than a cluster
Noroxi assessment
Priority: Monitor (action score 28/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.12% (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 06c0a0431b9856506fcd9b2c1b0c6136567d756d, 2c13e02592b918be7725ab5965e01ef4e46c4b57, 346314bb0cc2fc52b50b73d6ecc62e0217455c2e.
Low priority for now. Upgrade to Linux Linux 06c0a0431b9856506fcd9b2c1b0c6136567d756d, 2c13e02592b918be7725ab5965e01ef4e46c4b57, 346314bb0cc2fc52b50b73d6ecc62e0217455c2e 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: ocfs2: reject FITRIM ranges shorter than a cluster ocfs2_trim_mainbm() trims the global bitmap in cluster units, but its too-short range validation only checks sb->s_blocksize. On filesystems with a cluster size larger than the block size, a FITRIM range that is at least one block but shorter than one cluster is accepted and shifted down to len == 0. The later start + len - 1 and len -= ... arithmetic then underflows and can drive trimming past the requested range. Reject ranges shorter than s_clustersize instead. That preserves the existing -EINVAL behavior for requests that cannot discard even one allocation unit and keeps zero-cluster trims out of the group walk.
- Published
- Aug 15, 2026
- Updated
- Oct 16, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- —
Report tools
Action score
28
Monitor
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.1
- NVD has not scored this yet; the score shown is the CNA’s.
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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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.
—
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
- 3.14affected
- aa89762c54800208d5afdcd8e6bf124818f17fe0 and later · before d903d59c0315f59bdf0214b4f13d71c9feb2c45caffected · git
- aa89762c54800208d5afdcd8e6bf124818f17fe0 and later · before 441abb77222f155e8d931dbabb465466db01cfd7affected · git
- aa89762c54800208d5afdcd8e6bf124818f17fe0 and later · before e652d0f5108e447b22da4249bcd23dd1b63c73ddaffected · git
- aa89762c54800208d5afdcd8e6bf124818f17fe0 and later · before 346314bb0cc2fc52b50b73d6ecc62e0217455c2eaffected · git
- aa89762c54800208d5afdcd8e6bf124818f17fe0 and later · before 06c0a0431b9856506fcd9b2c1b0c6136567d756daffected · git
- aa89762c54800208d5afdcd8e6bf124818f17fe0 and later · before 3fa7139b5f42731a61f78c42433adae13f9adc21affected · git
- aa89762c54800208d5afdcd8e6bf124818f17fe0 and later · before 2c13e02592b918be7725ab5965e01ef4e46c4b57affected · git
- aa89762c54800208d5afdcd8e6bf124818f17fe0 and later · before ca1afd88f5eaaff9168e1466e5401385edf59543affected · git
- before 3.14not affected · semver
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.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-74347Aug 15, 2026 · netfilter: cttimeout: detach dataplane timeout policy and repurpose refcount31Monitor
- ← EarlierCVE-2026-74348Aug 15, 2026 · ocfs2/dlm: require a ref for locking_state debugfs open0Monitor
- Later →CVE-2026-74350Aug 15, 2026 · ocfs2: validate fast symlink target during inode read39Monitor
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 | 06c0a0431b9856506fcd9b2c1b0c6136567d756d | Vendor (CNA) |
| Linux Linux | 2c13e02592b918be7725ab5965e01ef4e46c4b57 | Vendor (CNA) |
| Linux Linux | 346314bb0cc2fc52b50b73d6ecc62e0217455c2e | Vendor (CNA) |
| Linux Linux | 3fa7139b5f42731a61f78c42433adae13f9adc21 | Vendor (CNA) |
| Linux Linux | 441abb77222f155e8d931dbabb465466db01cfd7 | Vendor (CNA) |
| Linux Linux | ca1afd88f5eaaff9168e1466e5401385edf59543 | Vendor (CNA) |
| Linux Linux | d903d59c0315f59bdf0214b4f13d71c9feb2c45c | Vendor (CNA) |
| Linux Linux | e652d0f5108e447b22da4249bcd23dd1b63c73dd | Vendor (CNA) |
| debian:linux | 6.1.180-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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
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
- 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
- None
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
nvd-secondary
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
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/2c13e02592b918be7725ab5965e01ef4e46c4b57
- git.kernel.org/stable/c/346314bb0cc2fc52b50b73d6ecc62e0217455c2e
- git.kernel.org/stable/c/3fa7139b5f42731a61f78c42433adae13f9adc21
- git.kernel.org/stable/c/441abb77222f155e8d931dbabb465466db01cfd7
- git.kernel.org/stable/c/ca1afd88f5eaaff9168e1466e5401385edf59543
- git.kernel.org/stable/c/d903d59c0315f59bdf0214b4f13d71c9feb2c45c
- git.kernel.org/stable/c/e652d0f5108e447b22da4249bcd23dd1b63c73dd
Vendor advisories and official records. Exploit/PoC links are deliberately left out.