CVE-2026-23452

MEDIUMNVD 4.74.7
EchelonGraph scoreMEDIUM confidence

Score 4.7 from GitHub Security Advisory published 2026-04-03. NVD baseline CVSS 4.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
4.7
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.7Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

PM: runtime: Fix a race condition related to device removal

The following code in pm_runtime_work() may dereference the dev->parent pointer after the parent device has been freed:

/* Maybe the parent is now able to suspend. */ if (parent && !parent->power.ignore_children) { spin_unlock(&dev->power.lock);

spin_lock(&parent->power.lock); rpm_idle(parent, RPM_ASYNC); spin_unlock(&parent->power.lock);

spin_lock(&dev->power.lock); }

Fix this by inserting a flush_work() call in pm_runtime_remove().

Without this patch blktest block/001 triggers the following complaint sporadically:

BUG: KASAN: slab-use-after-free in lock_acquire+0x70/0x160 Read of size 1 at addr ffff88812bef7198 by task kworker/u553:1/3081 Workqueue: pm pm_runtime_work Call Trace: dump_stack_lvl+0x61/0x80 print_address_description.constprop.0+0x8b/0x310 print_report+0xfd/0x1d7 kasan_report+0xd8/0x1d0 __kasan_check_byte+0x42/0x60 lock_acquire.part.0+0x38/0x230 lock_acquire+0x70/0x160 _raw_spin_lock+0x36/0x50 rpm_suspend+0xc6a/0xfe0 rpm_idle+0x578/0x770 pm_runtime_work+0xee/0x120 process_one_work+0xde3/0x1410 worker_thread+0x5eb/0xfe0 kthread+0x37b/0x480 ret_from_fork+0x6cb/0x920 ret_from_fork_asm+0x11/0x20

Allocated by task 4314: kasan_save_stack+0x2a/0x50 kasan_save_track+0x18/0x40 kasan_save_alloc_info+0x3d/0x50 __kasan_kmalloc+0xa0/0xb0 __kmalloc_noprof+0x311/0x990 scsi_alloc_target+0x122/0xb60 [scsi_mod] __scsi_scan_target+0x101/0x460 [scsi_mod] scsi_scan_channel+0x179/0x1c0 [scsi_mod] scsi_scan_host_selected+0x259/0x2d0 [scsi_mod] store_scan+0x2d2/0x390 [scsi_mod] dev_attr_store+0x43/0x80 sysfs_kf_write+0xde/0x140 kernfs_fop_write_iter+0x3ef/0x670 vfs_write+0x506/0x1470 ksys_write+0xfd/0x230 __x64_sys_write+0x76/0xc0 x64_sys_call+0x213/0x1810 do_syscall_64+0xee/0xfc0 entry_SYSCALL_64_after_hwframe+0x4b/0x53

Freed by task 4314: kasan_save_stack+0x2a/0x50 kasan_save_track+0x18/0x40 kasan_save_free_info+0x3f/0x50 __kasan_slab_free+0x67/0x80 kfree+0x225/0x6c0 scsi_target_dev_release+0x3d/0x60 [scsi_mod] device_release+0xa3/0x220 kobject_cleanup+0x105/0x3a0 kobject_put+0x72/0xd0 put_device+0x17/0x20 scsi_device_dev_release+0xacf/0x12c0 [scsi_mod] device_release+0xa3/0x220 kobject_cleanup+0x105/0x3a0 kobject_put+0x72/0xd0 put_device+0x17/0x20 scsi_device_put+0x7f/0xc0 [scsi_mod] sdev_store_delete+0xa5/0x120 [scsi_mod] dev_attr_store+0x43/0x80 sysfs_kf_write+0xde/0x140 kernfs_fop_write_iter+0x3ef/0x670 vfs_write+0x506/0x1470 ksys_write+0xfd/0x230 __x64_sys_write+0x76/0xc0 x64_sys_call+0x213/0x1810

CVSS v3
4.7
EG Score
4.7(medium)
EG Risk
26(Track)
EG Risk 26/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity47% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
0.6%
KEV
Not listed

Published

April 3, 2026

Last Modified

July 24, 2026

Advisory Details (10)

Auto-updated Jul 19, 2026
⚠️ Active exploitation confirmed. No patch confirmed yet.
generic

PM: runtime: Fix a race condition related to device removal - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/cf65a77c0f9531eb6cfb97cc040974d2d8fff043
generic

PM: runtime: Fix a race condition related to device removal - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c6febaacfb8a0aec7d771a0e6c21cd68102d5679
generic

PM: runtime: Fix a race condition related to device removal - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bb081fd37f8312651140d7429557258afe51693d
generic

PM: runtime: Fix a race condition related to device removal - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b6dd1a562ca8ba96c8ecb247c62b73f9fa02d47e
generic

PM: runtime: Fix a race condition related to device removal - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5649b46af8b167259e8a8e4e7eb3667ce74554b5
generic

PM: runtime: Fix a race condition related to device removal - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/39f2d86f2ddde8d1beda05732f30c7cd945e0b5a
generic

PM: runtime: Fix a race condition related to device removal - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/29ab768277617452d88c0607c9299cdc63b6e9ff
generic

PM: runtime: Fix a race condition related to device removal - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/20f6e2e22a9c6234113812d5f300d3e952a82721

Vendor Advisories for CVE-2026-23452(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.10.253osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 34× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 101 total refreshes for this CVE.

  1. 2026-07-24 14:17 UTCEPSS rescore
  2. 2026-07-23 14:18 UTCEPSS rescore
  3. 2026-07-23 14:18 UTCEPSS rescore
  4. 2026-07-23 03:07 UTCEG score recompute
  5. 2026-07-22 14:08 UTCEPSS rescore
  6. 2026-07-21 15:24 UTCEPSS rescore
  7. 2026-07-21 15:24 UTCEPSS rescore
  8. 2026-07-20 17:08 UTCEPSS rescore
  9. 2026-07-19 02:29 UTCEPSS rescore
  10. 2026-07-19 02:28 UTCEPSS rescore
  11. 2026-07-18 10:04 UTCEPSS rescore
  12. 2026-07-18 10:04 UTCEPSS rescore
  13. 2026-07-17 03:24 UTCOSV refresh
  14. 2026-07-16 17:03 UTCEPSS rescore
  15. 2026-07-16 17:03 UTCEPSS rescore
  16. 2026-07-15 16:57 UTCEPSS rescore
  17. 2026-07-15 16:57 UTCEPSS rescore
  18. 2026-07-14 13:19 UTCNVD updateCVSS v3 → 4.7 · severity → MEDIUM
  19. 2026-07-14 13:11 UTCMITRE cvelistV5
  20. 2026-07-13 22:30 UTCEPSS rescore
  21. 2026-07-12 05:46 UTCEPSS rescore
  22. 2026-07-12 05:46 UTCEPSS rescore
  23. 2026-07-11 08:27 UTCEPSS rescore
  24. 2026-07-09 19:10 UTCEPSS rescore
  25. 2026-07-08 15:15 UTCEPSS rescore
Show 75 more
  1. 2026-07-08 15:15 UTCEPSS rescore
  2. 2026-07-07 13:46 UTCEPSS rescore
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-06-30 23:22 UTCEPSS rescore
  6. 2026-06-30 23:22 UTCEPSS rescore
  7. 2026-06-28 04:56 UTCEPSS rescore
  8. 2026-06-28 04:56 UTCEPSS rescore
  9. 2026-06-27 03:08 UTCEPSS rescore
  10. 2026-06-21 01:59 UTCEPSS rescore
  11. 2026-06-21 01:59 UTCEPSS rescore
  12. 2026-06-18 17:52 UTCEPSS rescore
  13. 2026-06-17 17:53 UTCEPSS rescore
  14. 2026-06-17 17:53 UTCEPSS rescore
  15. 2026-06-16 17:52 UTCEPSS rescore
  16. 2026-06-15 17:48 UTCEPSS rescore
  17. 2026-06-14 23:18 UTCEPSS rescore
  18. 2026-06-13 23:00 UTCEPSS rescore
  19. 2026-06-12 23:12 UTCEPSS rescore
  20. 2026-06-12 23:12 UTCEPSS rescore
  21. 2026-06-11 22:03 UTCGHSA enrichment
  22. 2026-06-11 14:00 UTCEPSS rescore
  23. 2026-06-10 22:18 UTCEPSS rescore
  24. 2026-06-10 13:38 UTCGHSA enrichment
  25. 2026-06-10 13:22 UTCEPSS rescore
  26. 2026-06-09 14:33 UTCGHSA enrichment
  27. 2026-06-08 14:17 UTCEPSS rescore
  28. 2026-06-08 14:17 UTCEPSS rescore
  29. 2026-06-08 08:50 UTCGHSA enrichment
  30. 2026-06-07 15:25 UTCEPSS rescore
  31. 2026-06-07 15:24 UTCEPSS rescore
  32. 2026-06-07 10:56 UTCEG score recompute 4.70
  33. 2026-06-07 10:56 UTCGHSA enrichment
  34. 2026-06-06 13:47 UTCEPSS rescore
  35. 2026-06-06 13:47 UTCEPSS rescore
  36. 2026-06-06 13:47 UTCEPSS rescore
  37. 2026-06-05 22:47 UTCEPSS rescore
  38. 2026-06-05 06:10 UTCEPSS rescore
  39. 2026-06-05 06:10 UTCEPSS rescore
  40. 2026-06-04 13:12 UTCEPSS rescore
  41. 2026-06-04 13:12 UTCEPSS rescore
  42. 2026-06-04 13:12 UTCEPSS rescore
  43. 2026-06-02 20:13 UTCEPSS rescore
  44. 2026-06-02 20:13 UTCEPSS rescore
  45. 2026-06-01 13:51 UTCEPSS rescore
  46. 2026-06-01 13:51 UTCEPSS rescore
  47. 2026-06-01 13:51 UTCEPSS rescore
  48. 2026-05-31 22:30 UTCEPSS rescore
  49. 2026-05-31 22:30 UTCEPSS rescore
  50. 2026-05-31 00:16 UTCEPSS rescore
  51. 2026-05-31 00:16 UTCEPSS rescore
  52. 2026-05-31 00:16 UTCEPSS rescore
  53. 2026-05-29 13:44 UTCEPSS rescore
  54. 2026-05-29 13:44 UTCEPSS rescore
  55. 2026-05-28 13:44 UTCEPSS rescore
  56. 2026-05-28 13:44 UTCEPSS rescore
  57. 2026-05-28 13:44 UTCEPSS rescore
  58. 2026-05-27 13:40 UTCEPSS rescore
  59. 2026-05-27 13:40 UTCEPSS rescore
  60. 2026-05-27 13:40 UTCEPSS rescore
  61. 2026-05-26 13:44 UTCEPSS rescore
  62. 2026-05-26 13:44 UTCEPSS rescore
  63. 2026-05-26 07:18 UTCEPSS rescore
  64. 2026-05-26 07:18 UTCEPSS rescore
  65. 2026-05-26 07:18 UTCEPSS rescore
  66. 2026-05-22 21:16 UTCEPSS rescore
  67. 2026-05-21 22:43 UTCEPSS rescore
  68. 2026-05-20 22:38 UTCEPSS rescore
  69. 2026-05-20 22:37 UTCEPSS rescore
  70. 2026-05-20 22:37 UTCEPSS rescore
  71. 2026-05-20 19:15 UTCEG score recompute
  72. 2026-05-20 19:15 UTCGHSA enrichment
  73. 2026-05-20 11:22 UTCEPSS rescore
  74. 2026-05-20 11:21 UTCEPSS rescore
  75. 2026-05-20 11:21 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-23452?
CVE-2026-23452 is a medium vulnerability published on April 3, 2026. In the Linux kernel, the following vulnerability has been resolved: PM: runtime: Fix a race condition related to device removal The following code in pmruntimework() may dereference the dev->parent pointer after the parent device has been freed: / Maybe the parent is now able to suspend. / if…
When was CVE-2026-23452 disclosed?
CVE-2026-23452 was first published in the National Vulnerability Database on April 3, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-23452 actively exploited?
CVE-2026-23452 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-23452?
CVE-2026-23452 has a CVSS v3 base score of 4.7 (NVD).
How do I remediate CVE-2026-23452?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23452, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-23452

Explore →

Is Your Infrastructure Affected by CVE-2026-23452?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.