CVE-2023-53569: ext2: Check block size validity during mount
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.15% (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 0ebfaf14150f55550cffb1148ed3920143c7a69c, 22ab5fed07ad4b206ea910fd0132d1a0d4831584, 451b98155be5dfee05bc6e7c8b30c0be4add3f71.
Low priority for now. Upgrade to Linux Linux 0ebfaf14150f55550cffb1148ed3920143c7a69c, 22ab5fed07ad4b206ea910fd0132d1a0d4831584, 451b98155be5dfee05bc6e7c8b30c0be4add3f71 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: ext2: Check block size validity during mount Check that log of block size stored in the superblock has sensible value. Otherwise the shift computing the block size can overflow leading to undefined behavior.
- Published
- Oct 4, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 4th percentile
- CWE
- —
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel2.6.12.1 and later · before 4.14.316
- linux linux kernel4.15 and later · before 4.19.284
- linux linux kernel4.20 and later · before 5.4.244
- linux linux kernel5.5 and later · before 5.10.181
- linux linux kernel5.11 and later · before 5.15.113
- linux linux kernel5.16 and later · before 6.1.30
- linux linux kernel6.2 and later · before 6.3.4
- linux linux kernel2.6.12
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
- 2.6.12affected
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 0ebfaf14150f55550cffb1148ed3920143c7a69caffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 451b98155be5dfee05bc6e7c8b30c0be4add3f71affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before c4813f858e5c3e4c4659ce95385c1c400c593e1eaffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 22ab5fed07ad4b206ea910fd0132d1a0d4831584affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 99f8a15af6c9f0653193104a9e70891f950c6001affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before e6f4fb28890c1361e0db9eb1adee3fc04e7fe7f5affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before c2e7776843a953fd7e48895c3880c277f996193eaffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 62aeb94433fcec80241754b70d0d1836d5926b0aaffected · git
- before 2.6.12not 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.37-1 | 6.1.37-1 |
| Debian:13 | linux | before 6.3.7-1 | 6.3.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-2023-53567Oct 4, 2025 · spi: qup: Don't skip cleanup in remove's error path22Monitor
- ← EarlierCVE-2023-53568Oct 4, 2025 · s390/zcrypt: don't leak memory if dev_set_name() fails22Monitor
- Later →CVE-2023-53570Oct 4, 2025 · wifi: nl80211: fix integer overflow in nl80211_parse_mbssid_elems()31Monitor
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 | 0ebfaf14150f55550cffb1148ed3920143c7a69c | Vendor (CNA) |
| Linux Linux | 22ab5fed07ad4b206ea910fd0132d1a0d4831584 | Vendor (CNA) |
| Linux Linux | 451b98155be5dfee05bc6e7c8b30c0be4add3f71 | Vendor (CNA) |
| Linux Linux | 62aeb94433fcec80241754b70d0d1836d5926b0a | Vendor (CNA) |
| Linux Linux | 99f8a15af6c9f0653193104a9e70891f950c6001 | Vendor (CNA) |
| Linux Linux | c2e7776843a953fd7e48895c3880c277f996193e | Vendor (CNA) |
| Linux Linux | c4813f858e5c3e4c4659ce95385c1c400c593e1e | Vendor (CNA) |
| Linux Linux | e6f4fb28890c1361e0db9eb1adee3fc04e7fe7f5 | Vendor (CNA) |
| debian:linux | 6.1.37-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
- 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)
—
CVSS 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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/22ab5fed07ad4b206ea910fd0132d1a0d4831584
- git.kernel.org/stable/c/451b98155be5dfee05bc6e7c8b30c0be4add3f71
- git.kernel.org/stable/c/62aeb94433fcec80241754b70d0d1836d5926b0a
- git.kernel.org/stable/c/99f8a15af6c9f0653193104a9e70891f950c6001
- git.kernel.org/stable/c/c2e7776843a953fd7e48895c3880c277f996193e
- git.kernel.org/stable/c/c4813f858e5c3e4c4659ce95385c1c400c593e1e
- git.kernel.org/stable/c/e6f4fb28890c1361e0db9eb1adee3fc04e7fe7f5
Vendor advisories and official records. Exploit/PoC links are deliberately left out.