CVE-2026-74496

fou: Fix use-after-free in fou_create()

HIGH
7.8
CVSS Score
Published: August 15, 2026 at 12:27 PM UTC
Updated: October 16, 2026 at 08:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: fou: Fix use-after-free in fou_create() fou_create() publishes struct fou through sk_user_data before adding the new FOU port to the per-netns list. If fou_add_to_port_list() fails, the error path frees fou while it is still reachable through sk_user_data. A concurrent receive can then dereference the freed object in fou_from_sock(). This ordering issue was previously noted in the linked discussion. The failure is reachable when local port 0 is requested. Each socket binds to a different ephemeral port, but fou_cfg_cmp() compares the requested port 0 and reports -EALREADY once an entry already exists. Release the tunnel socket before freeing fou so sk_user_data is cleared first, and defer reclamation with kfree_rcu() to protect concurrent RCU readers. This matches the lifetime handling in fou_release().

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

23461551c00628c3f3fe9cf837bf53cf8f212b633.18
Vendor states this is fixed in 0ee628a58d83e571f36ec9f07624d6845e420c50 (fixed)
Vendor states this is fixed in 58835985c035a8333742f829ad7e0889a082f9d3 (fixed)
Vendor states this is fixed in 9042867d4701728f0c6527215b11471759904d8f (fixed)
Vendor states this is fixed in 99f4d3120b244f92e5df787152041296a2860cb5 (fixed)
Vendor states this is fixed in a28d8903bfe76089ea4bbdbff9976965f9ef8107 (fixed)
Vendor states this is fixed in a6fca682cfa2041e31aa72cc397c4a1406eb7468 (fixed)
Vendor states this is fixed in b14361aca6350ff7907b0e9903c7b94dc7d5d4a0 (fixed)
Vendor states this is fixed in b3f9c3e60aa25453774f899d25b5e61dd0bec1d5 (fixed)
Vendor states this is fixed in 3.18 (unaffected)
Vendor states this is fixed in 5.10.271 (unaffected)
Vendor states this is fixed in 5.15.222 (unaffected)
Vendor states this is fixed in 6.1.189 (unaffected)
Vendor states this is fixed in 6.12.111 (unaffected)
Vendor states this is fixed in 6.18.53 (unaffected)
Vendor states this is fixed in 6.6.158 (unaffected)
Vendor states this is fixed in 7.1.8 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card