CVE-2026-74436
Linux kernel vulnerability
- Published15 Aug 2026
Description
In the Linux kernel, the following vulnerability has been resolved: rxrpc: serialize kernel accept preallocation with socket teardown rxrpc_kernel_charge_accept() reads rx->backlog without any socket/backlog synchronization and passes that raw pointer into rxrpc_service_prealloc_one(). A concurrent rxrpc_discard_prealloc() sets rx->backlog = NULL and frees the backlog rings, so a kernel preallocation worker can keep using a freed struct rxrpc_backlog while updating *_backlog_head/tail and array slots. Serialize the state check and backlog lookup with the socket lock, and reject kernel preallocation once teardown has disabled listening or discarded the service backlog.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HRemediation
No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.
References
- https://git.kernel.org/stable/c/0337cdba0c477f176c0459bed012109453184573
- https://git.kernel.org/stable/c/11b429b84c87cb5a0152f14e7d6cb649ed363901
- https://git.kernel.org/stable/c/1741378a7a83dfd8e53a9196730df709b903cd33
- https://git.kernel.org/stable/c/35a967ff8b24db09ee429c39c5b5e6571639997d
- https://git.kernel.org/stable/c/c20d983968f239574290cf804a58cde18ad1c559
- https://git.kernel.org/stable/c/d6207326b4ca0ae1041281b6af9df53f8080669a
- https://git.kernel.org/stable/c/dc175389b18c29a5303ee83169ec653adfae3e17
- https://git.kernel.org/stable/c/dfa0b2bbc5e50119f89c6b5407faa5ed86dfa7c5
Frequently asked
Is CVE-2026-74436 being actively exploited?
CVE-2026-74436 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.76%.
How severe is CVE-2026-74436?
CVE-2026-74436 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.76% probability of exploitation.
How do I fix CVE-2026-74436?
Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-74436 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.