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-53158misc: fastrpc: Fix NULL pointer dereference in rpmsg callback

Description

In the Linux kernel, the following vulnerability has been resolved: misc: fastrpc: Fix NULL pointer dereference in rpmsg callback A NULL pointer dereference was observed on Hawi at boot when the DSP sends a glink message before fastrpc_rpmsg_probe() has completed initialization: Unable to handle kernel NULL pointer dereference at virtual address 0000000000000178 pc : _raw_spin_lock_irqsave+0x34/0x8c lr : fastrpc_rpmsg_callback+0x3c/0xcc [fastrpc] ... Call trace: _raw_spin_lock_irqsave+0x34/0x8c (P) fastrpc_rpmsg_callback+0x3c/0xcc [fastrpc] qcom_glink_native_rx+0x538/0x6a4 qcom_glink_smem_intr+0x14/0x24 [qcom_glink_smem] The faulting address 0x178 corresponds to the lock variable inside struct fastrpc_channel_ctx, confirming that cctx is NULL when fastrpc_rpmsg_callback() attempts to take the spinlock. There are two issues here. First, dev_set_drvdata() is called before spin_lock_init() and idr_init(), leaving a window where the callback can retrieve a valid cctx pointer but operate on an uninitialized spinlock. Second, the rpmsg channel becomes live as soon as the driver is bound, so fastrpc_rpmsg_callback() can fire before dev_set_drvdata() is called at all, resulting in dev_get_drvdata() returning NULL. Fix both issues by moving all cctx initialization ahead of dev_set_drvdata() so the structure is fully initialized before it becomes visible to the callback, and add a NULL check in fastrpc_rpmsg_callback() as a guard against any remaining window.

Timeline

  1. ID reserved

    By Linux

  2. · 16 days later

    Published

  3. · 9 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-53158, 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.12% · top 98% of all CVEs (15 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 f6f9279f2bf0e37e2f1fb119d8832b8568536a04 – < a3d91218ccca1e990bfb737b5a6da23f0afba22b
    • affected f6f9279f2bf0e37e2f1fb119d8832b8568536a04 – < 0d8c64511fd45690c5326f013710efcb4f73a97e
    • affected f6f9279f2bf0e37e2f1fb119d8832b8568536a04 – < 150bf6f1193c69252580c19d3b3cd631ddce61d7
    • affected f6f9279f2bf0e37e2f1fb119d8832b8568536a04 – < 8fb4a23df5b7c02929b62e5dbc270ec7c42b8134
    • affected f6f9279f2bf0e37e2f1fb119d8832b8568536a04 – < 4bfdf0a9855df55e9e031ca6a25b855820590c70
    • affected f6f9279f2bf0e37e2f1fb119d8832b8568536a04 – < d5de9cb5355db36438edc621dde3673e3f235767
    • affected f6f9279f2bf0e37e2f1fb119d8832b8568536a04 – < d77583ca33299fede0c194744ef2284e7ba5b763
    • affected f6f9279f2bf0e37e2f1fb119d8832b8568536a04 – < 5401fb4fe10fac6134c308495df18ed74aebb9c4
  • Linux · Linux

    • affected 5.1
    • unaffected < 5.1
    • unaffected 5.10.260 – ≤ 5.10.*
    • unaffected 5.15.211 – ≤ 5.15.*
    • unaffected 6.1.177 – ≤ 6.1.*
    • unaffected 6.6.143 – ≤ 6.6.*
    • unaffected 6.12.94 – ≤ 6.12.*
    • unaffected 6.18.36 – ≤ 6.18.*
    • unaffected 7.0.13 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .