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-2026-23309tracing: Add NULL pointer check to trigger_data_free()

Description

In the Linux kernel, the following vulnerability has been resolved: tracing: Add NULL pointer check to trigger_data_free() If trigger_data_alloc() fails and returns NULL, event_hist_trigger_parse() jumps to the out_free error path. While kfree() safely handles a NULL pointer, trigger_data_free() does not. This causes a NULL pointer dereference in trigger_data_free() when evaluating data->cmd_ops->set_filter. Fix the problem by adding a NULL pointer check to trigger_data_free(). The problem was found by an experimental code review agent based on gemini-3.1-pro while reviewing backports into v6.18.y.

Timeline

  1. ID reserved

    By Linux

  2. · 2 months later

    Published

  3. · 47 days 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-2026-23309, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.13% · top 97% of all CVEs (16 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected c10f0efe57728508d796ae4ba7abe4c14ec3d8ef – < 13dcd9269e225e4c4ceabdaeebe2ce4661b54c6e
    • affected 7e6556e9329bc484e9dcdab6e346d959267c0636 – < 59c15b9cc453b74beb9f04c6c398717e73612dc3
    • affected 9b0513905e0598b9f8cfccab8e47497aed5d935d – < 42b380f97d65e76e7b310facd525f730272daf57
    • affected 335dfe4bc6368e70e8c15419375cf609c4f85558 – < 2ce8ece5a78da67834db7728edc801889a64f643
    • affected e42efbe9754da78eafe11f6bd3ca9c8a094a752a – < 477469223b2b840f436ce204333de87cb17e5d93
    • affected 0550069cc25f513ce1f109c88f7c1f01d63297db – < 457965c13f0837a289c9164b842d0860133f6274
  • Linux · Linux

    • affected 6.1.165 – < 6.1.167
    • affected 6.6.128 – < 6.6.130
    • affected 6.12.75 – < 6.12.77
    • affected 6.18.14 – < 6.18.17
    • affected 6.19.4 – < 6.19.7

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .