Strix
57.4K

CVE-2026-74631

Unknown

Last modified

CVE-2026-74631 is a vulnerability of currently unknown severity. 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.

Description

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.

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 9014db202cb764b8e14c53e7bacc81f9a1a2ba7f, < 7ddc7af2ae7fc5a0c0635b245c0824c8b76de5cb; >= 9014db202cb764b8e14c53e7bacc81f9a1a2ba7f, < 07ad246529d136d5ef441d5ab4c305d132ff3090; >= 9014db202cb764b8e14c53e7bacc81f9a1a2ba7f, < c841789e456ec6751342fa800639ce8e82ff0e6b; >= 9014db202cb764b8e14c53e7bacc81f9a1a2ba7f, < af02c67ce654356c58db20a0bb2db33ace3b07a8; >= 9014db202cb764b8e14c53e7bacc81f9a1a2ba7f, < ca8342b5fc24c249fdb998468f6a168b457c67e5; >= 9014db202cb764b8e14c53e7bacc81f9a1a2ba7f, < 0b7d54cedea5cb158e21925ae0c6c2f5c87ed2a0; >= 9014db202cb764b8e14c53e7bacc81f9a1a2ba7f, < 4515c78f4d9fd577270f012efeb062ea58b3682d; >= 9014db202cb764b8e14c53e7bacc81f9a1a2ba7f, < 5d9686af2976741bbd79b150d1c9e60b81e7f12e
LinuxLinux4.18

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-74631?
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.
How severe is CVE-2026-74631?
Severity scoring for CVE-2026-74631 is pending analysis.
How do I fix CVE-2026-74631?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-74631?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST