CVE-2024-26673

netfilter: nft_ct: sanitize layer 3 and 4 protocol number in custom expectations

HIGH

7.1

CVSS Score

Published: April 2, 2024 at 06:51 AM UTC

Updated: June 17, 2026 at 07:18 AM UTC

2 products affected across 2 vendorsLinux KernelDebian Linux

Using Linux by Linux?

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

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

HIGH7.1

Exploit prediction

EPSS 0.2%

SSVC

No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_ct: sanitize layer 3 and 4 protocol number in custom expectations - Disallow families other than NFPROTO_{IPV4,IPV6,INET}. - Disallow layer 4 protocol with no ports, since destination port is a mandatory attribute for this object.

Affected

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

Debian Linux · Debiandrupal

95%

10.0

Linux Kernel · Linux

95%

5.11 ≤ v < 5.15.1495.16 ≤ v < 6.1.775.3 ≤ v < 5.10.2105.3 ≤ v < 5.15.1495.3 ≤ v < 5.4.2695.3 ≤ v < 6.1.775.3 ≤ v < 6.6.165.3 ≤ v < 6.7.45.3 ≤ v < 6.85.5 ≤ v < 5.10.2106.2 ≤ v < 6.6.166.7 ≤ v < 6.7.46.8 rc1 6.8 rc2857b46027d6f91150797295752581b7155b9d0e1

Vendor states this is fixed in 0f501dae16b7099e69ee9b0d5c70b8f40fd30e98 (fixed)

Vendor states this is fixed in 38cc1605338d99205a263707f4dde76408d3e0e8 (fixed)

Vendor states this is fixed in 65ee90efc928410c6f73b3d2e0afdd762652c09d (fixed)

Vendor states this is fixed in 8059918a1377f2f1fff06af4f5a4ed3d5acd6bc4 (fixed)

Vendor states this is fixed in b775ced05489f4b77a35fe203e9aeb22f428e38f (fixed)

Vendor states this is fixed in cfe3550ea5df292c9e2d608e8c4560032391847e (fixed)

Vendor states this is fixed in f549f340c91f08b938d60266e792ff7748dae483 (fixed)

Vendor states this is fixed in 5.10.210 (unaffected)

Vendor states this is fixed in 5.15.149 (unaffected)

Vendor states this is fixed in 5.3 (unaffected)

Vendor states this is fixed in 5.4.269 (unaffected)

Vendor states this is fixed in 6.1.77 (unaffected)