CVE-2023-53081
What it is
In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix data corruption after failed write When buffered write fails to copy data into underlying page cache page, ocfs2_write_end_nolock() just zeroes out and dirties the page. This can leave dirty page beyond EOF and if page writeback tries to write this page before write succeeds and expands i_size, page gets into inconsistent state where page dirty bit is clear but buffer dirty bits stay set resulting in page data never getting written and so data copied to the page is lost. Fix the problem by invalidating page beyond EOF after failed write.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 7.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Weakness
- CWE-787 · Out-of-bounds write
- Record status
- Analyzed
Affected
- Linux Kernel < 4.10
- Linux Kernel < 4.14.312
- Linux Kernel < 4.19.280
- Linux Kernel < 5.4.240
- Linux Kernel < 5.10.177
- Linux Kernel < 5.15.105
- Linux Kernel < 6.1.21
- Linux Kernel < 6.2.8
Attack profile CVSS 3.1 · 7.8
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2023-53081.md and follow it. Check whether this project is affected by CVE-2023-53081. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/1629f6f522b2d058019710466a84b240683bbee3
- https://git.kernel.org/stable/c/205759c6c18f54659b0b5976b14a52d1b3eb9f57
- https://git.kernel.org/stable/c/47eb055ad3588fc96d34e9e1dd87b210ce62906b
- https://git.kernel.org/stable/c/4c24eb49ab44351424ac8fe8567f91ea48a06089
- https://git.kernel.org/stable/c/90410bcf873cf05f54a32183afff0161f44f9715
- https://git.kernel.org/stable/c/91d7a4bd5656552d6259e2d0f8859f9e8cc5ef68
- https://git.kernel.org/stable/c/a9e53869cb43c96d6d851c491fd4e26430ab6ba6
- https://git.kernel.org/stable/c/c26f3ff4c0be590c1250f945ac2e4fc5fcdc5f45
References
- https://git.kernel.org/stable/c/1629f6f522b2d058019710466a84b240683bbee3
- https://git.kernel.org/stable/c/205759c6c18f54659b0b5976b14a52d1b3eb9f57
- https://git.kernel.org/stable/c/47eb055ad3588fc96d34e9e1dd87b210ce62906b
- https://git.kernel.org/stable/c/4c24eb49ab44351424ac8fe8567f91ea48a06089
- https://git.kernel.org/stable/c/90410bcf873cf05f54a32183afff0161f44f9715
- https://git.kernel.org/stable/c/91d7a4bd5656552d6259e2d0f8859f9e8cc5ef68
- https://git.kernel.org/stable/c/a9e53869cb43c96d6d851c491fd4e26430ab6ba6
- https://git.kernel.org/stable/c/c26f3ff4c0be590c1250f945ac2e4fc5fcdc5f45