CVE-2023-53081 [High] | Out-of-bounds Write in Linux Kernel

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.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.02%	0.17%	+0.15%
2	2026-06-12	0.06%	0.02%	-0.04%
3	2026-02-26	—	0.06%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.02%

0.17%

+0.15%

2026-06-12

0.06%

0.02%

-0.04%

2026-02-26

—

0.06%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
7.8	3.1	HIGH	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	5.9	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

7.8

3.1

HIGH

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

5.9

[email protected]

OS Trackers for CVE-2023-53081

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2023-53081 not yet assigned priority: Debian including 1 source packages (linux), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5.	https://security-tracker.debian.org/tracker/CVE-2023-53081
`redhat`	—	—	https://access.redhat.com/security/cve/CVE-2023-53081
`suse`	medium	—	https://www.suse.com/security/cve/CVE-2023-53081/
`ubuntu`	medium	CVE-2023-53081 medium priority: Ubuntu including 158 source packages (linux, linux-allwinner-5.19, …), 1551 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 1145, ignored 147, released 142, not-affected 101, needed 15, needs-triage 1.	https://ubuntu.com/security/CVE-2023-53081

Affected software / configurations for CVE-2023-53081

Vendor	Product	Version	Raw CPE
linux	linux_kernel	>= 4.9.242, < 4.10	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 4.14.204, < 4.14.312	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 4.19.155, < 4.19.280	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.4.75, < 5.4.240	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.9.5, < 5.10.177	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.11, < 5.15.105	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.16, < 6.1.21	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 6.2, < 6.2.8	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	6.3	cpe:2.3:o:linux:linux_kernel:6.3:rc1::::::
linux	linux_kernel	6.3	cpe:2.3:o:linux:linux_kernel:6.3:rc2::::::

References for CVE-2023-53081

URL	Tags
https://git.kernel.org/stable/c/1629f6f522b2d058019710466a84b240683bbee3	Patch
https://git.kernel.org/stable/c/205759c6c18f54659b0b5976b14a52d1b3eb9f57	Patch
https://git.kernel.org/stable/c/47eb055ad3588fc96d34e9e1dd87b210ce62906b	Patch
https://git.kernel.org/stable/c/4c24eb49ab44351424ac8fe8567f91ea48a06089	Patch
https://git.kernel.org/stable/c/90410bcf873cf05f54a32183afff0161f44f9715	Patch
https://git.kernel.org/stable/c/91d7a4bd5656552d6259e2d0f8859f9e8cc5ef68	Patch
https://git.kernel.org/stable/c/a9e53869cb43c96d6d851c491fd4e26430ab6ba6	Patch
https://git.kernel.org/stable/c/c26f3ff4c0be590c1250f945ac2e4fc5fcdc5f45	Patch

URL

CVE-2023-53081 | ocfs2: fix data corruption after failed write

Exploit prediction scoring system (EPSS) score for CVE-2023-53081

Common vulnerability scoring system (CVSS) metrics for CVE-2023-53081

Weakness enumeration for CVE-2023-53081

OS Trackers for CVE-2023-53081

Affected software / configurations for CVE-2023-53081

References for CVE-2023-53081