CVE-2022-48712

Kernel memory corruption via failed inode-array reallocation

Published Jun 20, 2024 · Updated May 11, 2026

Out-of-bounds write in Linux kernel ext4 fast-commit replay allows local users to corrupt kernel memory after an allocation failure. The ext4_fc_record_modified_inode() function enlarges fc_modified_inodes_size before krealloc() succeeds; after failure, later replay can skip reallocation and write through invalid array state. Low-privileged local access, ext4 fast-commit replay, and a failed allocation are required; the result is silent corruption or a kernel fault.

CVSS severity7.8
High
EPSS probability0.23%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Out-of-bounds write in Linux kernel ext4 fast-commit replay allows local users to corrupt kernel memory after an allocation failure. The ext4_fc_record_modified_inode() function enlarges fc_modified_inodes_size before krealloc() succeeds; after failure, later replay can skip reallocation and write through invalid array state. Low-privileged local access, ext4 fast-commit replay, and a failed allocation are required; the result is silent corruption or a kernel fault.

The record

CVE
CVE-2022-48712
Published
Jun 20, 2024
Updated
May 11, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
CWE-787, T1068
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Jun 20, 2024CVE publishedPublication date reported by the CVE source.
  2. May 11, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=5.10
  2. Affected versionversion=8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 <14aa3f49c7fc6424763f4323bfbc3a807b0727dc
  3. Affected versionversion=8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 <1b6762ecdf3cf12113772427c904aa3c420a1802
  4. Affected versionversion=8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 <62e46e0ffc02daa8fcfc02f7a932cc8a19601b19
  5. Affected versionversion=8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 <cdce59a1549190b66f8e3fe465c2b2f714b98a94

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=5.10; version=8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 <14aa3f49c7fc6424763f4323bfbc3a807b0727dc; version=8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 <1b6762ecdf3cf12113772427c904aa3c420a1802; version=8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 <62e46e0ffc02daa8fcfc02f7a932cc8a19601b19; version=8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 <cdce59a1549190b66f8e3fe465c2b2f714b98a94

Published CVSS scores

7.8NVDCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
7.8UbuntuCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-787Out-of-bounds Write
T1068Exploitation for Privilege Escalation

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo