gfs2: Fix NULL pointer dereference in gfs2_log_flush
- 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
- Fix
- Fixed in 5.15.200, 6.1.162, 6.6.37, 6.9.8
- 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
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: gfs2: Fix NULL pointer dereference in gfs2_log_flush In gfs2_jindex_free(), set sdp->sd_jdesc to NULL under the log flush lock to provide exclusion against gfs2_log_flush(). In gfs2_log_flush(), check if sdp->sd_jdesc is non-NULL before dereferencing it. Otherwise, we could run into a NULL pointer dereference when outstanding glock work races with an unmount (glock_work_func -> run_queue -> do_xmote -> inode_go_sync -> gfs2_log_flush).
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From 82218943058d5e3fe692a38b5a549479738dab33 · fixed in c3c5cfa3170c0940bc66a142859caac07d19b9d6; From 82218943058d5e3fe692a38b5a549479738dab33 · fixed in 5f6a84cfb33b34610623857bd93919dcb661e29b; From 82218943058d5e3fe692a38b5a549479738dab33 · fixed in 3429ef5f50909cee9e498c50f0c499b9397116ce; From 82218943058d5e3fe692a38b5a549479738dab33 · fixed in f54f9d5368a4e92ede7dd078a62788dae3a7c6ef; From 82218943058d5e3fe692a38b5a549479738dab33 · fixed in 35264909e9d1973ab9aaa2a1b07cda70f12bb828
- Linux Linux
5.12
- KernelLinux
From 5.12.0 · fixed in 5.15.200; From 5.16.0 · fixed in 6.1.162; From 6.2.0 · fixed in 6.6.37; From 6.7.0 · fixed in 6.9.8