net: smc: fix splice entry lifetime imbalance in smc_rx_splice
- 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.10.266, 5.15.217, 6.1.183, 6.6.152, 6.12.104, and 2 more
- 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: total
Summary
In the Linux kernel, the following vulnerability has been resolved: net: smc: fix splice entry lifetime imbalance in smc_rx_splice smc_rx_splice() passes pages to splice_to_pipe() before taking the references that cover the lifetime of each splice entry. In the VM-backed RMB path, splice_to_pipe() may drop unqueued entries through smc_rx_spd_release(), while queued entries are released later via the pipe buffer callback. The old post-splice accounting also derives the number of queued VM pages from an offset mutated while building the descriptor, and a multi-page splice pairs one sock_hold() with multiple sock_put() calls. Take the page and socket references for every candidate entry before splice_to_pipe(), and drop the matching private state, page reference, and socket reference from smc_rx_spd_release() for entries that never get queued. This fixes a refcount imbalance that can underflow page refcounts and trigger a use-after-free.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 9014db202cb764b8e14c53e7bacc81f9a1a2ba7f · fixed in 7ddc7af2ae7fc5a0c0635b245c0824c8b76de5cb; From 9014db202cb764b8e14c53e7bacc81f9a1a2ba7f · fixed in 07ad246529d136d5ef441d5ab4c305d132ff3090; From 9014db202cb764b8e14c53e7bacc81f9a1a2ba7f · fixed in c841789e456ec6751342fa800639ce8e82ff0e6b; From 9014db202cb764b8e14c53e7bacc81f9a1a2ba7f · fixed in af02c67ce654356c58db20a0bb2db33ace3b07a8; From 9014db202cb764b8e14c53e7bacc81f9a1a2ba7f · fixed in ca8342b5fc24c249fdb998468f6a168b457c67e5; From 9014db202cb764b8e14c53e7bacc81f9a1a2ba7f · fixed in 0b7d54cedea5cb158e21925ae0c6c2f5c87ed2a0; From 9014db202cb764b8e14c53e7bacc81f9a1a2ba7f · fixed in 4515c78f4d9fd577270f012efeb062ea58b3682d; From 9014db202cb764b8e14c53e7bacc81f9a1a2ba7f · fixed in 5d9686af2976741bbd79b150d1c9e60b81e7f12e
- Linux Linux
4.18
- KernelLinux
From 4.18.0 · fixed in 5.10.266; From 5.11.0 · fixed in 5.15.217; From 5.16.0 · fixed in 6.1.183; From 6.2.0 · fixed in 6.6.152; From 6.7.0 · fixed in 6.12.104; From 6.13.0 · fixed in 6.18.45; From 6.19.0 · fixed in 7.1.9
References 8
git.kernel.org
- stable/c/7ddc7af2ae7fc5a0c0635b245c0824c8b76de5cb
- stable/c/07ad246529d136d5ef441d5ab4c305d132ff3090
- stable/c/c841789e456ec6751342fa800639ce8e82ff0e6b
- stable/c/af02c67ce654356c58db20a0bb2db33ace3b07a8
- stable/c/ca8342b5fc24c249fdb998468f6a168b457c67e5
- stable/c/0b7d54cedea5cb158e21925ae0c6c2f5c87ed2a0
- stable/c/4515c78f4d9fd577270f012efeb062ea58b3682d
- stable/c/5d9686af2976741bbd79b150d1c9e60b81e7f12e