🛡️ CVE-2025-71304 — kernel

🟡 CVSS 5.5 — Medium ✅ No Known Exploit NVD
5.5
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

smack: /smack/doi: accept previously used values

In the Linux kernel, the following vulnerability has been resolved:

smack: /smack/doi: accept previously used values

Writing to /smack/doi a value that has ever been

written there in the past disables networking for

non-ambient labels.

E.g.

# cat /smack/doi

3

# netlabelctl -p cipso list

Configured CIPSO mappings (1)

DOI value : 3

mapping type : PASS_THROUGH

# netlabelctl -p map list

Configured NetLabel domain mappings (3)

domain: "_" (IPv4)

protocol: UNLABELED

domain: DEFAULT (IPv4)

protocol: CIPSO, DOI = 3

domain: DEFAULT (IPv6)

protocol: UNLABELED

# cat /smack/ambient

_

# cat /proc/$$/attr/smack/current

_

# ping -c1 10.1.95.12

64 bytes from 10.1.95.12: icmp_seq=1 ttl=64 time=0.964 ms

# echo foo >/proc/$$/attr/smack/current

# ping -c1 10.1.95.12

64 bytes from 10.1.95.12: icmp_seq=1 ttl=64 time=0.956 ms

unknown option 86

# echo 4 >/smack/doi

# echo 3 >/smack/doi

!> [ 214.050395] smk_cipso_doi:691 cipso add rc = -17

# echo 3 >/smack/doi

!> [ 249.402261] smk_cipso_doi:678 remove rc = -2

!> [ 249.402261] smk_cipso_doi:691 cipso add rc = -17

# ping -c1 10.1.95.12

!!> ping: 10.1.95.12: Address family for hostname not supported

# echo _ >/proc/$$/attr/smack/current

# ping -c1 10.1.95.12

64 bytes from 10.1.95.12: icmp_seq=1 ttl=64 time=0.617 ms

This happens because Smack keeps decommissioned DOIs,

fails to re-add them, and consequently refuses to add

the “default” domain map:

# netlabelctl -p cipso list

Configured CIPSO mappings (2)

DOI value : 3

mapping type : PASS_THROUGH

DOI value : 4

mapping type : PASS_THROUGH

# netlabelctl -p map list

Configured NetLabel domain mappings (2)

domain: "_" (IPv4)

protocol: UNLABELED

!> (no ipv4 map for default domain here)

domain: DEFAULT (IPv6)

protocol: UNLABELED

Fix by clearing decommissioned DOI definitions and

serializing concurrent DOI updates with a new lock.

Also:

  • allow /smack/doi to live unconfigured, since

adding a map (netlbl_cfg_cipsov4_map_add) may fail.

CIPSO_V4_DOI_UNKNOWN(0) indicates the unconfigured DOI

  • add new DOI before removing the old default map,

so the old map remains if the add fails

(2008-02-04, Casey Schaufler)

How this vulnerability can be exploited

This issue can be reached with local access to the system, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity none, availability high.

Affected software

CVE-2025-71304 is recorded against 3 packages.

  • kernel (from 6.19.0 up to 6.19.4)
  • linux-kernel (from 6.19 up to 6.19.4)
  • unknown

Timeline and source

Published on 27 May 2026 and last revised on 15 July 2026. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from NVD.

References

git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
github.com (Advisory)
nvd.nist.gov (Advisory)
git.kernel.org (Package)

CVE-2025-71304 on other distributions

Each distribution ships its own build and its own fixed version. Pick the one you run:

Details

Severity Medium
CVSS Score 5.5
CVSS Vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE N/A
Public Exploit ✅ No
Source NVD
Published 2026-05-27
Updated 2026-08-12
Modified 2026-07-15

Affected Packages

Software From version Fixed in
kernel 6.19.0 6.19.4
linux-kernel 6.19 6.19.4
unknown

References

Similar Threats

Vulnerability Monitoring

Track new vulnerabilities in kernel

CVE-2025-71304 is rated CVSS 5.5 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.

Set Up Free Alerts →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.