Kernel panic via freed journal dereference
Published Jun 23, 2023 · Updated Aug 2, 2024
NULL pointer dereference in Linux Kernel before 6.4-rc2 allows local users to cause a kernel panic via corrupt GFS2 filesystems. In gfs2_evict_inode, eviction references the journal descriptor after it has been freed and cleared, dereferencing NULL. The attacker needs privileged local access and a corrupt GFS2 filesystem; the bounded impact is denial of service through a kernel panic.
Summary
What happened
NULL pointer dereference in Linux Kernel before 6.4-rc2 allows local users to cause a kernel panic via corrupt GFS2 filesystems. In gfs2_evict_inode, eviction references the journal descriptor after it has been freed and cleared, dereferencing NULL. The attacker needs privileged local access and a corrupt GFS2 filesystem; the bounded impact is denial of service through a kernel panic.
The record
- CVE
- CVE-2023-3212
- Published
- Jun 23, 2023
- Updated
- Aug 2, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-476, T1499.001
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jun 23, 2023CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record 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.
- Affected versionversion=Fixed in kernel 6.4-rc2
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
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