LiveActive security incident?Get immediate response
CVE Record

CVE-2025-39974: tracing/osnoise: Fix slab-out-of-bounds in _parse_integer_limit()

In the Linux kernel, the following vulnerability has been resolved: tracing/osnoise: Fix slab-out-of-bounds in _parse_integer_limit() When config osnoise cpus by write() syscall, the following KASAN splat may be observed: BUG: KASAN: slab-out-of-bounds in _parse_integer_limit+0x103/0x130 Read of size 1 at addr ffff88810121e3a1 by task test/447 CPU: 1 UID: 0 PID: 447 Comm: test Not tainted 6.17.0-rc6-dirty #288 PREEMPT(voluntary) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014 Call Trace: <TASK> dump_stack_lvl+0x55/0x70 print_report+0xcb/0x610 kasan_report+0xb8/0xf0 _parse_integer_limit+0x103/0x130 bitmap_parselist+0x16d/0x6f0 osnoise_cpus_write+0x116/0x2d0 vfs_write+0x21e/0xcc0 ksys_write+0xee/0x1c0 do_syscall_64+0xa8/0x2a0 entry_SYSCALL_64_after_hwframe+0x77/0x7f </TASK> This issue can be reproduced by below code: const char *cpulist = "1"; int fd=open("/sys/kernel/debug/tracing/osnoise/cpus", O_WRONLY); write(fd, cpulist, strlen(cpulist)); Function bitmap_parselist() was called to parse cpulist, it require that the parameter 'buf' must be terminated with a '\0' or '\n'. Fix this issue by adding a '\0' to 'buf' in osnoise_cpus_write().

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2025-39974 is a Linux kernel bug in the osnoise tracing interface. A specially shaped write to the osnoise CPU configuration path can trigger an out-of-bounds slab read. The public record shows it is fixed upstream, but does not show active exploitation or a CVSS score.

Executive priority

Prioritize routine patching for Linux systems where untrusted local users or workloads may access kernel tracing. Escalate if affected kernels run on shared compute, developer hosts, or container platforms with exposed debug interfaces.

Technical view

The flaw is in tracing/osnoise osnoise_cpus_write(), which passes a buffer to bitmap_parselist() without the required null or newline terminator. This can cause _parse_integer_limit() to read past the allocated buffer. Reported affected kernel lines include 6.16, 6.16.10, and 6.17 entries in the CVE data.

Likely exposure

Exposure appears limited to systems running affected Linux kernels with the osnoise tracing debugfs interface available to users able to write to it. The sources do not confirm remote exploitability.

Exploitation context

The CVE record includes a local reproduction scenario using the osnoise cpus tracing file. There is no KEV listing and no cited source claiming active exploitation in the wild.

Researcher notes

Public evidence indicates a bounds-read bug fixed by terminating the osnoise input buffer before bitmap parsing. Impact is not fully characterized in the sources beyond KASAN slab-out-of-bounds read. No public exploit status is provided.

Mitigation direction

  • Apply a vendor kernel update containing the referenced Linux stable fixes.
  • If building kernels, include the upstream stable commits cited for this CVE.
  • Check distribution advisories for exact affected and fixed package versions.
  • Limit access to kernel tracing/debug interfaces according to vendor hardening guidance.

Validation and detection

  • Inventory Linux kernel versions on servers and appliances.
  • Check whether vendor kernel packages include the referenced stable fixes.
  • Review whether debugfs tracing interfaces are enabled and accessible.
  • Avoid production reproduction; validate through version and patch presence.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-39974 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
3Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux17f89102fe23d7389085a8820550df688f79888a, 17f89102fe23d7389085a8820550df688f79888aunaffected
LinuxLinux6.16, 0, 6.16.10, 6.17affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.