BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-23306High confidence

scsi: pm8001: Fix use-after-free in pm8001_queue_command()

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 34 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 5 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.13% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 34 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

24 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 20 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.85-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.170-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.19.8-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.19.8-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fdeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-23306 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: scsi: pm8001: Fix use-after-free in pm8001_queue_command()
14 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel as a component of Red Hat Enterprise Linux 6
  • kernel-abi-whitelists as a component of Red Hat Enterprise Linux 6
  • kernel-bootwrapper as a component of Red Hat Enterprise Linux 6
  • kernel-debug as a component of Red Hat Enterprise Linux 6
  • kernel-debug-devel as a component of Red Hat Enterprise Linux 6
  • kernel-devel as a component of Red Hat Enterprise Linux 6
  • kernel-doc as a component of Red Hat Enterprise Linux 6
  • kernel-firmware as a component of Red Hat Enterprise Linux 6
  • kernel-headers as a component of Red Hat Enterprise Linux 6
  • kernel-kdump as a component of Red Hat Enterprise Linux 6
  • kernel-kdump-devel as a component of Red Hat Enterprise Linux 6
  • kernel.src as a component of Red Hat Enterprise Linux 6
Summary
A flaw was found in the Linux kernel, specifically within the `pm8001` SCSI driver and the `libsas` library. An incorrect return value in the `pm8001_queue_command()` function, when a physical device is down or gone, can lead to a double free vulnerability. This occurs because the function frees a Serial Attached SCSI (SAS) task but then returns an error, causing the `libsas` layer to attempt to free the same task again. This double free can result in system instability or a denial of service (DoS).
Remediation
Out of support scope
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-15246

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 34 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: scsi: pm8001: Fix use-after-free in pm8001_queue_command() Commit e29c47fe8946 ("scsi: pm8001: Simplify pm8001_task_exec()") refactors pm8001_queue_command(), however it introduces a potential cause of a double free scenario when it changes the function to return -ENODEV in case of phy down/device gone state. In this path, pm8001_queue_command() updates task status and calls task_done to indicate to upper layer that the task has been handled. However, this also frees the underlying SAS task. A -ENODEV is then returned to the caller. When libsas sas_ata_qc_issue() receives this error value, it assumes the task wasn't handled/queued by LLDD and proceeds to clean up and free the task again, resulting in a double free. Since pm8001_queue_command() handles the SAS task in this case, it should return 0 to the caller indicating that the task has been handled.

What

In the Linux kernel, the following vulnerability has been resolved: scsi: pm8001: Fix use-after-free in pm8001_queue_command() Commit e29c47fe8946 ("scsi: pm8001: Simplify pm8001_task_exec()") refactors pm8001_queue_command(), however it introduces a potential cause of a double free scenario when it changes the function to return -ENODEV in case of phy down/device gone state. In this path, pm8001_queue_command() updates task status and calls task_done to indicate to upper layer that the task has been handled. However, this also frees the underlying SAS task. A -ENODEV is then returned to the caller. When libsas sas_ata_qc_issue() receives this error value, it assumes the task wasn't handled/queued by LLDD and proceeds to clean up and free the task again, resulting in a double free. Since pm8001_queue_command() handles the SAS task in this case, it should return 0 to the caller indicating that the task has been handled.

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: scsi: pm8001: Fix use-after-free in pm8001_queue_command() Commit e29c47fe8946 ("scsi: pm8001: Simplify pm8001_task_exec()") refactors pm8001_queue_command(), however it introduces a potential cause of a double free scenario when it changes the function to return -ENODEV in case of phy down/device gone state. In this path, pm8001_queue_command() updates task status and calls task_done to indicate to upper layer that the task has been handled. However, this also frees the underlying SAS task. A -ENODEV is then returned to the caller. When libsas sas_ata_qc_issue() receives this error value, it assumes the task wasn't handled/queued by LLDD and proceeds to clean up and free the task again, resulting in a double free. Since pm8001_queue_command() handles the SAS task in this case, it should return 0 to the caller indicating that the task has been handled.

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → Use After Free → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-416 ↗

CWE-416: Use After Free. The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-416
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-0861Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service zu verursachen, Sicherheitsmaßnahmen zu umgehen, Informationen offenzulegen, weitere nicht spezifizierte Auswirkungen zu verursachen und potentiell Code auszuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260401Security Bulletin 01 Apr 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 01 Apr 2026, published on 1 April 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1255Multiples vulnérabilités dans le noyau Linux de SUSE

-2026:23967-1 du 29 septembre 2026 https://www.suse.com/support/update/announcement/2026/suse-su-202623967-1 Bulletin de sécurité SUSE SUSE-SU-2026:23968-1 du 29 septembre 2026 https://www.suse.com/support/update/announcement/2026/suse-su-202623968-1 Référence CVE CVE-2025-68214 https://www.cve.org/CVERecord?id=CVE-2025-68214 Référence CVE CVE-2025-68358 https://www.cve.org/CVERecord?id=CVE-2025-68358 Référence CVE CVE-2025-68780 https://www.cve.org/CVERecord?id=CVE-2025-68780 Référence CVE CVE-2025-71075 https://www.cve.org/CVERecord?id=CVE-2025-71075 Référence CVE CVE-2026-23113 https://www.cve.org/CVERecord?id=CVE-2026-23113 Référence CVE CVE-2026-23306 https://www.cve.org/CVERecord?id=CVE-2026-23306 Référence CVE CVE-2026-23348 https://www.cve.org/CVERecord?id=CVE-2026-23348 Référence CVE CVE-2026-31418 https://www.cve.org/CVERecord?id=CVE-2026-31418 Référence CVE CVE-2026-31530 https://www.cve.org/CVERecord?id=CVE-2026-31530 Référence CVE CVE-2026-31531 https://www.cve.org/CVERecord?id=CVE-2026-31531 Référence CVE CVE-2026-43116 https://www.cve.org/CVERecord?id=CVE-2026-43116 Référence CVE CVE-2026-43125 https://www.cve.org/CVERecord?id=CVE-2026-43125 Référence CVE CVE-2026-43163 https://www.cve.org/CVERecord?id=CVE-2026-43163 Référence CVE CVE-2026-43239 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1066Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-23291 Référence CVE CVE-2026-23292 https://www.cve.org/CVERecord?id=CVE-2026-23292 Référence CVE CVE-2026-23293 https://www.cve.org/CVERecord?id=CVE-2026-23293 Référence CVE CVE-2026-23296 https://www.cve.org/CVERecord?id=CVE-2026-23296 Référence CVE CVE-2026-23298 https://www.cve.org/CVERecord?id=CVE-2026-23298 Référence CVE CVE-2026-23300 https://www.cve.org/CVERecord?id=CVE-2026-23300 Référence CVE CVE-2026-23302 https://www.cve.org/CVERecord?id=CVE-2026-23302 Référence CVE CVE-2026-23303 https://www.cve.org/CVERecord?id=CVE-2026-23303 Référence CVE CVE-2026-23304 https://www.cve.org/CVERecord?id=CVE-2026-23304 Référence CVE CVE-2026-23306 https://www.cve.org/CVERecord?id=CVE-2026-23306 Référence CVE CVE-2026-23307 https://www.cve.org/CVERecord?id=CVE-2026-23307 Référence CVE CVE-2026-23308 https://www.cve.org/CVERecord?id=CVE-2026-23308 Référence CVE CVE-2026-23310 https://www.cve.org/CVERecord?id=CVE-2026-23310 Référence CVE CVE-2026-23312 https://www.cve.org/CVERecord?id=CVE-2026-23312 Référence CVE CVE-2026-23313 https://www.cve.org/CVERecord?id=CVE-2026-23313 Référence CVE CVE-2026-23315 https://www.cve.org/CVERecord?id=CVE-2026-23315 Référence CVE CVE-2026-23317 https://www.cve.org/CVERecord?id=CVE-2026-23317 Référence CVE CVE-2026-23318 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0954Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-23291 Référence CVE CVE-2026-23292 https://www.cve.org/CVERecord?id=CVE-2026-23292 Référence CVE CVE-2026-23293 https://www.cve.org/CVERecord?id=CVE-2026-23293 Référence CVE CVE-2026-23296 https://www.cve.org/CVERecord?id=CVE-2026-23296 Référence CVE CVE-2026-23298 https://www.cve.org/CVERecord?id=CVE-2026-23298 Référence CVE CVE-2026-23300 https://www.cve.org/CVERecord?id=CVE-2026-23300 Référence CVE CVE-2026-23302 https://www.cve.org/CVERecord?id=CVE-2026-23302 Référence CVE CVE-2026-23303 https://www.cve.org/CVERecord?id=CVE-2026-23303 Référence CVE CVE-2026-23304 https://www.cve.org/CVERecord?id=CVE-2026-23304 Référence CVE CVE-2026-23306 https://www.cve.org/CVERecord?id=CVE-2026-23306 Référence CVE CVE-2026-23307 https://www.cve.org/CVERecord?id=CVE-2026-23307 Référence CVE CVE-2026-23308 https://www.cve.org/CVERecord?id=CVE-2026-23308 Référence CVE CVE-2026-23310 https://www.cve.org/CVERecord?id=CVE-2026-23310 Référence CVE CVE-2026-23312 https://www.cve.org/CVERecord?id=CVE-2026-23312 Référence CVE CVE-2026-23313 https://www.cve.org/CVERecord?id=CVE-2026-23313 Référence CVE CVE-2026-23315 https://www.cve.org/CVERecord?id=CVE-2026-23315 Référence CVE CVE-2026-23317 https://www.cve.org/CVERecord?id=CVE-2026-23317 Référence CVE CVE-2026-23318 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0926Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-23291 Référence CVE CVE-2026-23292 https://www.cve.org/CVERecord?id=CVE-2026-23292 Référence CVE CVE-2026-23293 https://www.cve.org/CVERecord?id=CVE-2026-23293 Référence CVE CVE-2026-23296 https://www.cve.org/CVERecord?id=CVE-2026-23296 Référence CVE CVE-2026-23298 https://www.cve.org/CVERecord?id=CVE-2026-23298 Référence CVE CVE-2026-23300 https://www.cve.org/CVERecord?id=CVE-2026-23300 Référence CVE CVE-2026-23302 https://www.cve.org/CVERecord?id=CVE-2026-23302 Référence CVE CVE-2026-23303 https://www.cve.org/CVERecord?id=CVE-2026-23303 Référence CVE CVE-2026-23304 https://www.cve.org/CVERecord?id=CVE-2026-23304 Référence CVE CVE-2026-23306 https://www.cve.org/CVERecord?id=CVE-2026-23306 Référence CVE CVE-2026-23307 https://www.cve.org/CVERecord?id=CVE-2026-23307 Référence CVE CVE-2026-23308 https://www.cve.org/CVERecord?id=CVE-2026-23308 Référence CVE CVE-2026-23310 https://www.cve.org/CVERecord?id=CVE-2026-23310 Référence CVE CVE-2026-23312 https://www.cve.org/CVERecord?id=CVE-2026-23312 Référence CVE CVE-2026-23313 https://www.cve.org/CVERecord?id=CVE-2026-23313 Référence CVE CVE-2026-23315 https://www.cve.org/CVERecord?id=CVE-2026-23315 Référence CVE CVE-2026-23317 https://www.cve.org/CVERecord?id=CVE-2026-23317 Référence CVE CVE-2026-23318 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0697Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-23273 Référence CVE CVE-2026-23274 https://www.cve.org/CVERecord?id=CVE-2026-23274 Référence CVE CVE-2026-23276 https://www.cve.org/CVERecord?id=CVE-2026-23276 Référence CVE CVE-2026-23279 https://www.cve.org/CVERecord?id=CVE-2026-23279 Référence CVE CVE-2026-23290 https://www.cve.org/CVERecord?id=CVE-2026-23290 Référence CVE CVE-2026-23291 https://www.cve.org/CVERecord?id=CVE-2026-23291 Référence CVE CVE-2026-23298 https://www.cve.org/CVERecord?id=CVE-2026-23298 Référence CVE CVE-2026-23300 https://www.cve.org/CVERecord?id=CVE-2026-23300 Référence CVE CVE-2026-23304 https://www.cve.org/CVERecord?id=CVE-2026-23304 Référence CVE CVE-2026-23306 https://www.cve.org/CVERecord?id=CVE-2026-23306 Référence CVE CVE-2026-23307 https://www.cve.org/CVERecord?id=CVE-2026-23307 Référence CVE CVE-2026-23308 https://www.cve.org/CVERecord?id=CVE-2026-23308 Référence CVE CVE-2026-23312 https://www.cve.org/CVERecord?id=CVE-2026-23312 Référence CVE CVE-2026-23313 https://www.cve.org/CVERecord?id=CVE-2026-23313 Référence CVE CVE-2026-23315 https://www.cve.org/CVERecord?id=CVE-2026-23315 Référence CVE CVE-2026-23316 https://www.cve.org/CVERecord?id=CVE-2026-23316 Référence CVE CVE-2026-23317 https://www.cve.org/CVERecord?id=CVE-2026-23317 Référence CVE CVE-2026-23318 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0547Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2026-23290 Référence CVE CVE-2026-23291 https://www.cve.org/CVERecord?id=CVE-2026-23291 Référence CVE CVE-2026-23292 https://www.cve.org/CVERecord?id=CVE-2026-23292 Référence CVE CVE-2026-23293 https://www.cve.org/CVERecord?id=CVE-2026-23293 Référence CVE CVE-2026-23296 https://www.cve.org/CVERecord?id=CVE-2026-23296 Référence CVE CVE-2026-23298 https://www.cve.org/CVERecord?id=CVE-2026-23298 Référence CVE CVE-2026-23300 https://www.cve.org/CVERecord?id=CVE-2026-23300 Référence CVE CVE-2026-23303 https://www.cve.org/CVERecord?id=CVE-2026-23303 Référence CVE CVE-2026-23304 https://www.cve.org/CVERecord?id=CVE-2026-23304 Référence CVE CVE-2026-23306 https://www.cve.org/CVERecord?id=CVE-2026-23306 Référence CVE CVE-2026-23307 https://www.cve.org/CVERecord?id=CVE-2026-23307 Référence CVE CVE-2026-23312 https://www.cve.org/CVERecord?id=CVE-2026-23312 Référence CVE CVE-2026-23315 https://www.cve.org/CVERecord?id=CVE-2026-23315 Référence CVE CVE-2026-23317 https://www.cve.org/CVERecord?id=CVE-2026-23317 Référence CVE CVE-2026-23318 https://www.cve.org/CVERecord?id=CVE-2026-23318 Référence CVE CVE-2026-23319 https://www.cve.org/CVERecord?id=CVE-2026-23319 Référence CVE CVE-2026-23321 https://www.cve.org/CVERecord?id=CVE-2026-23321 Référence CVE CVE-2026-23324 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0548Multiples vulnérabilités dans le noyau Linux de Debian

d?id=CVE-2026-23292 Référence CVE CVE-2026-23293 https://www.cve.org/CVERecord?id=CVE-2026-23293 Référence CVE CVE-2026-23296 https://www.cve.org/CVERecord?id=CVE-2026-23296 Référence CVE CVE-2026-23297 https://www.cve.org/CVERecord?id=CVE-2026-23297 Référence CVE CVE-2026-23298 https://www.cve.org/CVERecord?id=CVE-2026-23298 Référence CVE CVE-2026-23300 https://www.cve.org/CVERecord?id=CVE-2026-23300 Référence CVE CVE-2026-23302 https://www.cve.org/CVERecord?id=CVE-2026-23302 Référence CVE CVE-2026-23303 https://www.cve.org/CVERecord?id=CVE-2026-23303 Référence CVE CVE-2026-23304 https://www.cve.org/CVERecord?id=CVE-2026-23304 Référence CVE CVE-2026-23306 https://www.cve.org/CVERecord?id=CVE-2026-23306 Référence CVE CVE-2026-23307 https://www.cve.org/CVERecord?id=CVE-2026-23307 Référence CVE CVE-2026-23308 https://www.cve.org/CVERecord?id=CVE-2026-23308 Référence CVE CVE-2026-23310 https://www.cve.org/CVERecord?id=CVE-2026-23310 Référence CVE CVE-2026-23312 https://www.cve.org/CVERecord?id=CVE-2026-23312 Référence CVE CVE-2026-23313 https://www.cve.org/CVERecord?id=CVE-2026-23313 Référence CVE CVE-2026-23315 https://www.cve.org/CVERecord?id=CVE-2026-23315 Référence CVE CVE-2026-23316 https://www.cve.org/CVERecord?id=CVE-2026-23316 Référence CVE CVE-2026-23317 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0376Multiples vulnérabilités dans les produits Microsoft

ulletin de sécurité Microsoft CVE-2026-23289 du 26 mars 2026 Bulletin de sécurité Microsoft CVE-2026-23290 du 26 mars 2026 Bulletin de sécurité Microsoft CVE-2026-23291 du 26 mars 2026 Bulletin de sécurité Microsoft CVE-2026-23292 du 26 mars 2026 Bulletin de sécurité Microsoft CVE-2026-23293 du 26 mars 2026 Bulletin de sécurité Microsoft CVE-2026-23296 du 26 mars 2026 Bulletin de sécurité Microsoft CVE-2026-23298 du 26 mars 2026 Bulletin de sécurité Microsoft CVE-2026-23300 du 26 mars 2026 Bulletin de sécurité Microsoft CVE-2026-23303 du 26 mars 2026 Bulletin de sécurité Microsoft CVE-2026-23304 du 26 mars 2026 Bulletin de sécurité Microsoft CVE-2026-23306 du 26 mars 2026 Bulletin de sécurité Microsoft CVE-2026-23307 du 26 mars 2026 Bulletin de sécurité Microsoft CVE-2026-23310 du 26 mars 2026 Bulletin de sécurité Microsoft CVE-2026-23312 du 26 mars 2026 Bulletin de sécurité Microsoft CVE-2026-23315 du 26 mars 2026 Bulletin de sécurité Microsoft CVE-2026-23317 du 26 mars 2026 Bulletin de sécurité Microsoft CVE-2026-23318 du 26 mars 2026 Bulletin de sécurité Microsoft CVE-2026-23319 du 26 mars 2026 Bulletin de sécurité Microsoft CVE-2026-23324 du 26 mars 2026 Bulletin de sécurité Microsoft CVE-2026-23334 du 26 mars 2026 Bulletin de sécurité Microsoft CVE-2026-23336 du 26 mars 2026 Bulletin de s

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-017396LinuxのLinux Kernelにおける解放済みメモリの使用に関する脆弱性

Linuxカーネルにおけるscsi: pm8001ドライバのpm8001_queue_command()関数にUse-After-Freeの脆弱性が存在していました。コミットe29c47fe8946によるリファクタリングで、phyのダウンやデバイス消失時に-ENODEVを返す処理が追加されましたが、この処理によりSASタスクの状態を正しく管理できず、二重解放が発生する恐れがありました。具体的には、pm8001_queue_command()がタスクを処理済みと示すために0を返すべきところを-ENODEVを返したため、libsasの上位層がタスクを重複して解放してしまう問題でした。この問題は、pm8001_queue_command()が状況に応じて正しく0を返すように修正され、解決しました。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 5.18, 6.1.167 ≤ 6.1.*, 6.6.130 ≤ 6.6.*, 6.12.77 ≤ 6.12.*, 6.18.17 ≤ 6.18.*, 6.19.7 ≤ 6.19.*, 7.0 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 25 Mar 2026 · Last source change 5 Aug 2026, 12:21 UTC · CWE-416 · Use After Free

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-15246
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceNIST NVD
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-15246↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-23306 · cve.blacktree.nl