Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-37923tracing: Fix oob write in trace_seq_to_buffer()

Description

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 Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025 Call Trace: <TASK> __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:408 [inline] print_report+0xc3/0x670 mm/kasan/report.c:521 kasan_report+0xe0/0x110 mm/kasan/report.c:634 check_region_inline mm/kasan/generic.c:183 [inline] kasan_check_range+0xef/0x1a0 mm/kasan/generic.c:189 __asan_memcpy+0x3c/0x60 mm/kasan/shadow.c:106 trace_seq_to_buffer kernel/trace/trace.c:1830 [inline] tracing_splice_read_pipe+0x6be/0xdd0 kernel/trace/trace.c:6822 .... ================================================================== It has been reported that trace_seq_to_buffer() tries to copy more data than PAGE_SIZE to buf. Therefore, to prevent this, we should use the smaller of trace_seq_used(&iter->seq) and PAGE_SIZE as an argument.

Timeline

  1. ID reserved

    By Linux

  2. · 34 days later

    Published

  3. · 15 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-37923, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.25% · top 84% of all CVEs (18 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 3c56819b14b00dd449bd776303e61f8532fad09f – < f4b0174e9f18aaba59ee6ffdaf8827a7f94eb606
    • affected 3c56819b14b00dd449bd776303e61f8532fad09f – < 665ce421041890571852422487f4c613d1824ba9
    • affected 3c56819b14b00dd449bd776303e61f8532fad09f – < 1a3f9482b50b74fa9421bff8ceecfefd0dc06f8f
    • affected 3c56819b14b00dd449bd776303e61f8532fad09f – < 441021e5b3c7d9bd1b963590652c415929f3b157
    • affected 3c56819b14b00dd449bd776303e61f8532fad09f – < 056ebbddb8faf4ddf83d005454dd78fc25c2d897
    • affected 3c56819b14b00dd449bd776303e61f8532fad09f – < 1f27a3e93b8d674b24b27fcdbc6f72743cd96c0d
    • affected 3c56819b14b00dd449bd776303e61f8532fad09f – < c5d2b66c5ef5037b4b4360e5447605ff00ba1bd4
    • affected 3c56819b14b00dd449bd776303e61f8532fad09f – < f5178c41bb43444a6008150fe6094497135d07cb
  • Linux · Linux

    • affected 2.6.30
    • unaffected < 2.6.30
    • unaffected 5.4.294 – ≤ 5.4.*
    • unaffected 5.10.238 – ≤ 5.10.*
    • unaffected 5.15.182 – ≤ 5.15.*
    • unaffected 6.1.138 – ≤ 6.1.*
    • unaffected 6.6.90 – ≤ 6.6.*
    • unaffected 6.12.28 – ≤ 6.12.*
    • unaffected 6.14.6 – ≤ 6.14.*
    • unaffected 6.15 – ≤ *

References

References10

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-37923 badge
[![CVE-2025-37923](https://cveledger.app/badge/CVE-2025-37923.svg)](https://cveledger.app/cve/CVE-2025-37923)

Record last updated .