Review reviewHigh

CVE-2025-37923

Linux Linux, linux kernel, debian linux

In the Linux kernel, the following vulnerability has been resolved: tracing: Fix oob write in trace_seq_to_buffer() syzbot reported this bug: ================================================================== BUG: KASAN: slab-out-of-bounds in trace_seq_to_buffer kernel/trace/trace.c:1830 [inline] BUG: KASAN: slab-out-of-bounds in tracing_splice_read_pipe+0x6be/0xdd0 kernel/trace/trace.c:6822 Write of size 4507 at addr ffff888032b6b000 by task syz.2.320/7260 CPU: 1 UID: 0 PID: 7260 Comm: syz.2.320 Not tainted 6.15.0-rc1-syzkaller-00301-g3bde70a2c827 #0 PREEMPT(full) Hardware name: Google Goo...

CVSS
7.8
EPSS
0.19%
8.76% percentile
CISA KEV
Not listed
Published
2025.05.21
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.19%
Technical severityCVSS 7.8

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: tracing: Fix oob write in trace_seq_to_buffer() syzbot reported this bug: ================================================================== BUG: KASAN: slab-out-of-bounds in trace_seq_to_buffer kernel/trace/trace.c:1830 [inline] BUG: KASAN: slab-out-of-bounds in tracing_splice_read_pipe+0x6be/0xdd0 kernel/trace/trace.c:6822 Write of size 4507 at addr ffff888032b6b000 by task syz.2.320/7260 CPU: 1 UID: 0 PID: 7260 Comm: syz.2.320 Not tainted 6.15.0-rc1-syzkaller-00301-g3bde70a2c827 #0 PREEMPT(full) Hardware name: Google Goo...

Affected product and versions

Product
Linux Linux, linux kernel, debian linux
Affected versions
>= 3c56819b14b00dd449bd776303e61f8532fad09f < f4b0174e9f18aaba59ee6ffdaf8827a7f94eb606, >= 3c56819b14b00dd449bd776303e61f8532fad09f < 665ce421041890571852422487f4c613d1824ba9, >= 3c56819b14b00dd449bd776303e61f8532fad09f < 1a3f9482b50b74fa9421bff8ceecfefd0dc06f8f, >= 3c56819b14b00dd449bd776303e61f8532fad09f < 441021e5b3c7d9bd1b963590652c415929f3b157, >= 3c56819b14b00dd449bd776303e61f8532fad09f < 056ebbddb8faf4ddf83d005454dd78fc25c2d897, >= 3c56819b14b00dd449bd776303e61f8532fad09f < 1f27a3e93b8d674b24b27fcdbc6f72743cd96c0d, >= 3c56819b14b00dd449bd776303e61f8532fad09f < c5d2b66c5ef5037b4b4360e5447605ff00ba1bd4, >= 3c56819b14b00dd449bd776303e61f8532fad09f < f5178c41bb43444a6008150fe6094497135d07cb, >= 2.6.30, >= 2.6.30 < 5.4.294, >= 5.5 < 5.10.238, >= 5.11 < 5.15.182, >= 5.16 < 6.1.138, >= 6.2 < 6.6.90, >= 6.7 < 6.12.28, >= 6.13 < 6.14.6, 6.15, 11.0
Fixed versions
5.4.294, 5.10.238, 5.15.182, 6.1.138, 6.6.90, 6.12.28, 6.14.6

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel, debian linux and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-787