CVE-2025-68818

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-01-13. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 6 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

scsi: Revert "scsi: qla2xxx: Perform lockless command completion in abort path"

This reverts commit 0367076b0817d5c75dfb83001ce7ce5c64d803a9.

The commit being reverted added code to __qla2x00_abort_all_cmds() to call sp->done() without holding a spinlock. But unlike the older code below it, this new code failed to check sp->cmd_type and just assumed TYPE_SRB, which results in a jump to an invalid pointer in target-mode with TYPE_TGT_CMD:

qla2xxx [0000:65:00.0]-d034:8: qla24xx_do_nack_work create sess success 0000000009f7a79b qla2xxx [0000:65:00.0]-5003:8: ISP System Error - mbx1=1ff5h mbx2=10h mbx3=0h mbx4=0h mbx5=191h mbx6=0h mbx7=0h. qla2xxx [0000:65:00.0]-d01e:8: -> fwdump no buffer qla2xxx [0000:65:00.0]-f03a:8: qla_target(0): System error async event 0x8002 occurred qla2xxx [0000:65:00.0]-00af:8: Performing ISP error recovery - ha=0000000058183fda. BUG: kernel NULL pointer dereference, address: 0000000000000000 PF: supervisor instruction fetch in kernel mode PF: error_code(0x0010) - not-present page PGD 0 P4D 0 Oops: 0010 [#1] SMP CPU: 2 PID: 9446 Comm: qla2xxx_8_dpc Tainted: G O 6.1.133 #1 Hardware name: Supermicro Super Server/X11SPL-F, BIOS 4.2 12/15/2023 RIP: 0010:0x0 Code: Unable to access opcode bytes at 0xffffffffffffffd6. RSP: 0018:ffffc90001f93dc8 EFLAGS: 00010206 RAX: 0000000000000282 RBX: 0000000000000355 RCX: ffff88810d16a000 RDX: ffff88810dbadaa8 RSI: 0000000000080000 RDI: ffff888169dc38c0 RBP: ffff888169dc38c0 R08: 0000000000000001 R09: 0000000000000045 R10: ffffffffa034bdf0 R11: 0000000000000000 R12: ffff88810800bb40 R13: 0000000000001aa8 R14: ffff888100136610 R15: ffff8881070f7400 FS: 0000000000000000(0000) GS:ffff88bf80080000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffffffffffffffd6 CR3: 000000010c8ff006 CR4: 00000000003706e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: ? __die+0x4d/0x8b ? page_fault_oops+0x91/0x180 ? trace_buffer_unlock_commit_regs+0x38/0x1a0 ? exc_page_fault+0x391/0x5e0 ? asm_exc_page_fault+0x22/0x30 __qla2x00_abort_all_cmds+0xcb/0x3e0 [qla2xxx_scst] qla2x00_abort_all_cmds+0x50/0x70 [qla2xxx_scst] qla2x00_abort_isp_cleanup+0x3b7/0x4b0 [qla2xxx_scst] qla2x00_abort_isp+0xfd/0x860 [qla2xxx_scst] qla2x00_do_dpc+0x581/0xa40 [qla2xxx_scst] kthread+0xa8/0xd0

Then commit 4475afa2646d ("scsi: qla2xxx: Complete command early within lock") added the spinlock back, because not having the lock caused a race and a crash. But qla2x00_abort_srb() in the switch below already checks for qla2x00_chip_is_down() and handles it the same way, so the code above the switch is now redundant and still buggy in target-mode. Remove it.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
44(Track)
EG Risk 44/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
Severity88% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
18%
KEV
Not listed

Published

January 13, 2026

Last Modified

July 30, 2026

Advisory Details (8)

Auto-updated Jul 30, 2026
No patch confirmed yet.
generic

scsi: Revert "scsi: qla2xxx: Perform lockless command completion in abort path" - kernel/git/stable/linux.git - Linux kernel stable tree

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

scsi: Revert "scsi: qla2xxx: Perform lockless command completion in abort path" - kernel/git/stable/linux.git - Linux kernel stable tree

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

scsi: Revert "scsi: qla2xxx: Perform lockless command completion in abort path" - kernel/git/stable/linux.git - Linux kernel stable tree

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

scsi: Revert "scsi: qla2xxx: Perform lockless command completion in abort path" - kernel/git/stable/linux.git - Linux kernel stable tree

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

scsi: Revert "scsi: qla2xxx: Perform lockless command completion in abort path" - kernel/git/stable/linux.git - Linux kernel stable tree

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

scsi: Revert "scsi: qla2xxx: Perform lockless command completion in abort path" - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/50b097d92c99f718831b8b349722bc79f718ba1b
generic

scsi: Revert "scsi: qla2xxx: Perform lockless command completion in abort path" - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1c728951bc769b795d377852eae1abddad88635d

Vendor Advisories for CVE-2025-68818(2)

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

Patch Availability(31)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-nvidia-tegra-igx-rt-5.15 (5.15.0.1044.46) @ jammy2026-07-30ubuntu
ubuntulinux-tools-realtime-5.15 (5.15.0.1102.106) @ jammy2026-07-30ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1097.95) @ jammy2026-07-30ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1109.94) @ jammy2026-07-30ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1109.107) @ jammy2026-07-30ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.17.0-22.22) @ questing2026-07-30ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1067 (5.15.0-1067.71) @ jammy2026-07-30ubuntu
ubuntulinux-virtual-6.8 (6.8.0-110.110) @ noble2026-07-30ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.17.0-1010.11~24.04.1) @ noble2026-07-30ubuntu
ubuntulinux-tools-gcp-64k-6.17 (6.17.0-1012.12) @ questing2026-07-30ubuntu
ubuntulinux-tools-6.8.1-1047-realtime (6.8.1-1047.48~22.04.1) @ jammy2026-07-30ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1054.57+fips1) @ noble2026-07-30ubuntu
ubuntulinux-tools-nvidia-64k-6.8 (6.8.0-1051.54) @ noble2026-07-30ubuntu
ubuntulinux-tools-oracle-64k-6.17 (6.17.0-1011.11) @ questing2026-07-30ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1052.56) @ noble2026-07-30ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1049.50) @ noble2026-07-30ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2042.43) @ noble2026-07-30ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1051.54.1) @ noble2026-07-30ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1054.57~22.04.1) @ jammy2026-07-30ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1110.119~20.04.1) @ focal2026-07-30ubuntu
ubuntulinux-tools-oem-6.17 (6.17.0-1020.20) @ noble2026-07-30ubuntu
ubuntulinux-tools-raspi-6.17 (6.17.0-1014.14) @ questing2026-07-30ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1054.60) @ noble2026-07-30ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1054.60+fips1) @ noble2026-07-30ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1029.30) @ noble2026-07-30ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1022.22) @ noble2026-07-30ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1059.65~22.04.1) @ jammy2026-07-30ubuntu
ubuntulinux-tools-gke-5.15 (5.15.0.1099.98) @ jammy2026-07-30ubuntu
ubuntulinux-tools-gcp-fips-5.15 (5.15.0.1103.93) @ jammy2026-07-30ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1094.98) @ jammy2026-07-30ubuntu
linuxKernel @ 5.10.248osv

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.

Additional Vendor Advisories

(24)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 16× in last 7d / 52× 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 138 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2025-68818?
CVE-2025-68818 is a high vulnerability published on January 13, 2026. In the Linux kernel, the following vulnerability has been resolved: scsi: Revert "scsi: qla2xxx: Perform lockless command completion in abort path" This reverts commit 0367076b0817d5c75dfb83001ce7ce5c64d803a9. The commit being reverted added code to qla2x00abortall_cmds() to call sp->done() without…
When was CVE-2025-68818 disclosed?
CVE-2025-68818 was first published in the National Vulnerability Database on January 13, 2026, with the most recent update on July 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-68818 actively exploited?
CVE-2025-68818 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 82.0% of all scored CVEs.
What is the CVSS score of CVE-2025-68818?
CVE-2025-68818 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2025-68818?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-68818, 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-2025-68818

Explore →

Is Your Infrastructure Affected by CVE-2025-68818?

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