CVE-2023-53285
ext4: add bounds checking in get_max_inline_xattr_value_size()
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
In the Linux kernel, the following vulnerability has been resolved: ext4: add bounds checking in get_max_inline_xattr_value_size() Normally the extended attributes in the inode body would have been checked when the inode is first opened, but if someone is writing to the block device while the file system is mounted, it's possible for the inode table to get corrupted. Add bounds checking to avoid reading beyond the end of allocated memory if this happens.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
3.8
References 9
git.kernel.org
- stable/c/5a229d21b98d132673096710e8281ef522dab1d1
- stable/c/3d7b8fbcd2273e2b9f4c6de5ce2f4c0cd3cb1205
- stable/c/486efbbc9445dca7890a1b86adbccb88b91284b0
- stable/c/4597554b4f7b29e7fd78aa449bab648f8da4ee2c
- stable/c/f22b274429e88d3dc7e79d375b56ce4f2f59f0b4
- stable/c/1d2caddbeeee56fbbc36b428c5b909c3ad88eb7f
- stable/c/e780058bd75614b66882bc02620ddbd884171560
- stable/c/88a06a94942c5c0a896e9da1113a6bb29e36cbef
- stable/c/2220eaf90992c11d888fe771055d4de330385f01