xfs: handle NULL b_addr in xfs_buf_free
- 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 6.12.114, 6.18.45, 7.1.9
- 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
Summary
In the Linux kernel, the following vulnerability has been resolved: xfs: handle NULL b_addr in xfs_buf_free When xfs_buf_alloc_backing_mem() fails, xfs_buf_free() is called with bp->b_addr still NULL. The code falls through to the folio_put path which calls virt_to_folio(NULL), dereferencing an invalid address and causing a kernel crash. Call Trace: xfs_buf_free+0x25f/0x510 xfs_buf_alloc+0xc98/0x19b0 xfs_buf_find_insert+0x55/0x14d0 xfs_buf_get_map+0x122b/0x17c0 xfbtree_init_leaf_block+0x11c/0x4a0 xfbtree_init+0x1bb/0x460 xrep_rmap_setup_scan+0x100/0x1f0 xrep_rmapbt+0x41/0xc0 Fix this by skipping folio_put() when bp->b_addr is NULL.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 5076a6040ca1613e616d84aecfaac5f932db84e0 · fixed in 444ff50ece93060131ad84fbd3f378723d8ac243; From 5076a6040ca1613e616d84aecfaac5f932db84e0 · fixed in ccf6738adcafa5ddbddc4e71b45d8a51b86643c7; From 5076a6040ca1613e616d84aecfaac5f932db84e0 · fixed in 3aa0c1d23ee1b9d9b340fb2f4736536e1408d706; From 5076a6040ca1613e616d84aecfaac5f932db84e0 · fixed in d852729c5f4f830fbe7413df032e29459b3daf83
- Linux Linux
6.9
- KernelLinux
From 6.9.0 · fixed in 6.12.114; From 6.13.0 · fixed in 6.18.45; From 6.19.0 · fixed in 7.1.9