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

efi: Allocate runtime workqueue before ACPI init

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 20 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 severityMediumOperational priority:Low, lowered one band.downgradedsince 19 Jul 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.16% 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: No default targetRemediation target: Normal maintenance

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 20 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.94-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.12-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.12-1Debian Security Tracker ↗Source updated 6 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-64183 · CSAF 2.0 · revision 11 · interimSUSE Product Security TeamCVE-2026-64183
47 known affected

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

  • cluster-md-kmp-default as component of SUSE Linux Enterprise Server 15 SP6-LTSS
  • dlm-kmp-default as component of SUSE Linux Enterprise Server 15 SP6-LTSS
  • gfs2-kmp-default as component of SUSE Linux Enterprise Server 15 SP6-LTSS
  • kernel-default as component of SUSE Linux Enterprise Server 15 SP6-LTSS
  • kernel-default-devel as component of SUSE Linux Enterprise Server 15 SP6-LTSS
  • kernel-devel as component of SUSE Linux Enterprise Server 15 SP6-LTSS
  • kernel-macros as component of SUSE Linux Enterprise Server 15 SP6-LTSS
  • kernel-source as component of SUSE Linux Enterprise Server 15 SP6-LTSS
  • ocfs2-kmp-default as component of SUSE Linux Enterprise Server 15 SP6-LTSS
  • reiserfs-kmp-default as component of SUSE Linux Enterprise Server 15 SP6-LTSS
  • cluster-md-kmp-default as component of SUSE Linux Enterprise Server 15 SP6
  • dlm-kmp-default as component of SUSE Linux Enterprise Server 15 SP6
Summary
In the Linux kernel, the following vulnerability has been resolved: efi: Allocate runtime workqueue before ACPI init Since commit 5894cf571e14 ("acpi/prmt: Use EFI runtime sandbox to invoke PRM handlers") ACPI PRM calls are delegated to a workqueue which runs in a kernel thread, making it easier to detect and mitigate faulting memory accesses performed by the firmware. Rafael reports that such PRM accesses may occur before efisubsys_init() executes, which is where the workqueue is allocated, leading to NULL pointer dereferences. Since acpi_init() [which triggers the early PRM accesses] executes as a subsys_initcall() as well, and has its own dependencies that may be sensitive to initcall ordering, deferring acpi_init() is not an option. So instead, split off the workqueue allocation into its own postcore initcall, as this is the only missing piece to allow EFI runtime calls to be made. This ensures that EFI runtime call (including PRM calls) are accessible to all code running at subsys_initcall() level.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
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-45868

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

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 20 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: efi: Allocate runtime workqueue before ACPI init Since commit 5894cf571e14 ("acpi/prmt: Use EFI runtime sandbox to invoke PRM handlers") ACPI PRM calls are delegated to a workqueue which runs in a kernel thread, making it easier to detect and mitigate faulting memory accesses performed by the firmware. Rafael reports that such PRM accesses may occur before efisubsys_init() executes, which is where the workqueue is allocated, leading to NULL pointer dereferences. Since acpi_init() [which triggers the early PRM accesses] executes as a subsys_initcall() as well, and has its own dependencies that may be sensitive to initcall ordering, deferring acpi_init() is not an option. So instead, split off the workqueue allocation into its own postcore initcall, as this is the only missing piece to allow EFI runtime calls to be made. This ensures that EFI runtime call (including PRM calls) are accessible to all code running at subsys_initcall() level.

What

In the Linux kernel, the following vulnerability has been resolved: efi: Allocate runtime workqueue before ACPI init Since commit 5894cf571e14 ("acpi/prmt: Use EFI runtime sandbox to invoke PRM handlers") ACPI PRM calls are delegated to a workqueue which runs in a kernel thread, making it easier to detect and mitigate faulting memory accesses performed by the firmware. Rafael reports that such PRM accesses may occur before efisubsys_init() executes, which is where the workqueue is allocated, leading to NULL pointer dereferences. Since acpi_init() [which triggers the early PRM accesses] executes as a subsys_initcall() as well, and has its own dependencies that may be sensitive to initcall ordering, deferring acpi_init() is not an option. So instead, split off the workqueue allocation into its own postcore initcall, as this is the only missing piece to allow EFI runtime calls to be made. This ensures that EFI runtime call (including PRM calls) are accessible to all code running at subsys_initcall() level.

Why

The product dereferences a pointer that it expects to be valid but is NULL.

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: efi: Allocate runtime workqueue before ACPI init Since commit 5894cf571e14 ("acpi/prmt: Use EFI runtime sandbox to invoke PRM handlers") ACPI PRM calls are delegated to a workqueue which runs in a kernel thread, making it easier to detect and mitigate faulting memory accesses performed by the firmware. Rafael reports that such PRM accesses may occur before efisubsys_init() executes, which is where the workqueue is allocated, leading to NULL pointer dereferences. Since acpi_init() [which triggers the early PRM accesses] executes as a subsys_initcall() as well, and has its own dependencies that may be sensitive to initcall ordering, deferring acpi_init() is not an option. So instead, split off the workqueue allocation into its own postcore initcall, as this is the only missing piece to allow EFI runtime calls to be made. This ensures that EFI runtime call (including PRM calls) are accessible to all code running at subsys_initcall() level.

Why

The product dereferences a pointer that it expects to be valid but is NULL.

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 → NULL Pointer Dereference → 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-476 ↗

CWE-476: NULL Pointer Dereference. The product dereferences a pointer that it expects to be valid but is NULL.

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:N/I:N/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.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.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-476
A

Official authority intelligence

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

BSI · German · WID-SEC-2026-2403Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260722Security Bulletin 22 Jul 2026

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

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

d?id=CVE-2026-64174 Référence CVE CVE-2026-64175 https://www.cve.org/CVERecord?id=CVE-2026-64175 Référence CVE CVE-2026-64176 https://www.cve.org/CVERecord?id=CVE-2026-64176 Référence CVE CVE-2026-64177 https://www.cve.org/CVERecord?id=CVE-2026-64177 Référence CVE CVE-2026-64178 https://www.cve.org/CVERecord?id=CVE-2026-64178 Référence CVE CVE-2026-64179 https://www.cve.org/CVERecord?id=CVE-2026-64179 Référence CVE CVE-2026-64180 https://www.cve.org/CVERecord?id=CVE-2026-64180 Référence CVE CVE-2026-64181 https://www.cve.org/CVERecord?id=CVE-2026-64181 Référence CVE CVE-2026-64182 https://www.cve.org/CVERecord?id=CVE-2026-64182 Référence CVE CVE-2026-64183 https://www.cve.org/CVERecord?id=CVE-2026-64183 Référence CVE CVE-2026-64184 https://www.cve.org/CVERecord?id=CVE-2026-64184 Référence CVE CVE-2026-64185 https://www.cve.org/CVERecord?id=CVE-2026-64185 Référence CVE CVE-2026-64186 https://www.cve.org/CVERecord?id=CVE-2026-64186 Référence CVE CVE-2026-64187 https://www.cve.org/CVERecord?id=CVE-2026-64187 Référence CVE CVE-2026-64188 https://www.cve.org/CVERecord?id=CVE-2026-64188 Référence CVE CVE-2026-64189 https://www.cve.org/CVERecord?id=CVE-2026-64189 Référence CVE CVE-2026-64191 https://www.cve.org/CVERecord?id=CVE-2026-64191 Référence CVE CVE-2026-64192 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64174 Référence CVE CVE-2026-64175 https://www.cve.org/CVERecord?id=CVE-2026-64175 Référence CVE CVE-2026-64176 https://www.cve.org/CVERecord?id=CVE-2026-64176 Référence CVE CVE-2026-64177 https://www.cve.org/CVERecord?id=CVE-2026-64177 Référence CVE CVE-2026-64178 https://www.cve.org/CVERecord?id=CVE-2026-64178 Référence CVE CVE-2026-64179 https://www.cve.org/CVERecord?id=CVE-2026-64179 Référence CVE CVE-2026-64180 https://www.cve.org/CVERecord?id=CVE-2026-64180 Référence CVE CVE-2026-64181 https://www.cve.org/CVERecord?id=CVE-2026-64181 Référence CVE CVE-2026-64182 https://www.cve.org/CVERecord?id=CVE-2026-64182 Référence CVE CVE-2026-64183 https://www.cve.org/CVERecord?id=CVE-2026-64183 Référence CVE CVE-2026-64184 https://www.cve.org/CVERecord?id=CVE-2026-64184 Référence CVE CVE-2026-64185 https://www.cve.org/CVERecord?id=CVE-2026-64185 Référence CVE CVE-2026-64186 https://www.cve.org/CVERecord?id=CVE-2026-64186 Référence CVE CVE-2026-64187 https://www.cve.org/CVERecord?id=CVE-2026-64187 Référence CVE CVE-2026-64188 https://www.cve.org/CVERecord?id=CVE-2026-64188 Référence CVE CVE-2026-64189 https://www.cve.org/CVERecord?id=CVE-2026-64189 Référence CVE CVE-2026-64191 https://www.cve.org/CVERecord?id=CVE-2026-64191 Référence CVE CVE-2026-64192 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64168 Référence CVE CVE-2026-64170 https://www.cve.org/CVERecord?id=CVE-2026-64170 Référence CVE CVE-2026-64173 https://www.cve.org/CVERecord?id=CVE-2026-64173 Référence CVE CVE-2026-64174 https://www.cve.org/CVERecord?id=CVE-2026-64174 Référence CVE CVE-2026-64177 https://www.cve.org/CVERecord?id=CVE-2026-64177 Référence CVE CVE-2026-64178 https://www.cve.org/CVERecord?id=CVE-2026-64178 Référence CVE CVE-2026-64179 https://www.cve.org/CVERecord?id=CVE-2026-64179 Référence CVE CVE-2026-64180 https://www.cve.org/CVERecord?id=CVE-2026-64180 Référence CVE CVE-2026-64182 https://www.cve.org/CVERecord?id=CVE-2026-64182 Référence CVE CVE-2026-64183 https://www.cve.org/CVERecord?id=CVE-2026-64183 Référence CVE CVE-2026-64184 https://www.cve.org/CVERecord?id=CVE-2026-64184 Référence CVE CVE-2026-64185 https://www.cve.org/CVERecord?id=CVE-2026-64185 Référence CVE CVE-2026-64187 https://www.cve.org/CVERecord?id=CVE-2026-64187 Référence CVE CVE-2026-64188 https://www.cve.org/CVERecord?id=CVE-2026-64188 Référence CVE CVE-2026-64189 https://www.cve.org/CVERecord?id=CVE-2026-64189 Référence CVE CVE-2026-64191 https://www.cve.org/CVERecord?id=CVE-2026-64191 Référence CVE CVE-2026-64192 https://www.cve.org/CVERecord?id=CVE-2026-64192 Référence CVE CVE-2026-64205 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64174 Référence CVE CVE-2026-64175 https://www.cve.org/CVERecord?id=CVE-2026-64175 Référence CVE CVE-2026-64176 https://www.cve.org/CVERecord?id=CVE-2026-64176 Référence CVE CVE-2026-64177 https://www.cve.org/CVERecord?id=CVE-2026-64177 Référence CVE CVE-2026-64178 https://www.cve.org/CVERecord?id=CVE-2026-64178 Référence CVE CVE-2026-64179 https://www.cve.org/CVERecord?id=CVE-2026-64179 Référence CVE CVE-2026-64180 https://www.cve.org/CVERecord?id=CVE-2026-64180 Référence CVE CVE-2026-64181 https://www.cve.org/CVERecord?id=CVE-2026-64181 Référence CVE CVE-2026-64182 https://www.cve.org/CVERecord?id=CVE-2026-64182 Référence CVE CVE-2026-64183 https://www.cve.org/CVERecord?id=CVE-2026-64183 Référence CVE CVE-2026-64184 https://www.cve.org/CVERecord?id=CVE-2026-64184 Référence CVE CVE-2026-64185 https://www.cve.org/CVERecord?id=CVE-2026-64185 Référence CVE CVE-2026-64186 https://www.cve.org/CVERecord?id=CVE-2026-64186 Référence CVE CVE-2026-64187 https://www.cve.org/CVERecord?id=CVE-2026-64187 Référence CVE CVE-2026-64188 https://www.cve.org/CVERecord?id=CVE-2026-64188 Référence CVE CVE-2026-64189 https://www.cve.org/CVERecord?id=CVE-2026-64189 Référence CVE CVE-2026-64191 https://www.cve.org/CVERecord?id=CVE-2026-64191 Référence CVE CVE-2026-64192 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-63991 Référence CVE CVE-2026-63994 https://www.cve.org/CVERecord?id=CVE-2026-63994 Référence CVE CVE-2026-64025 https://www.cve.org/CVERecord?id=CVE-2026-64025 Référence CVE CVE-2026-64089 https://www.cve.org/CVERecord?id=CVE-2026-64089 Référence CVE CVE-2026-64106 https://www.cve.org/CVERecord?id=CVE-2026-64106 Référence CVE CVE-2026-64114 https://www.cve.org/CVERecord?id=CVE-2026-64114 Référence CVE CVE-2026-64174 https://www.cve.org/CVERecord?id=CVE-2026-64174 Référence CVE CVE-2026-64179 https://www.cve.org/CVERecord?id=CVE-2026-64179 Référence CVE CVE-2026-64182 https://www.cve.org/CVERecord?id=CVE-2026-64182 Référence CVE CVE-2026-64183 https://www.cve.org/CVERecord?id=CVE-2026-64183 Référence CVE CVE-2026-64187 https://www.cve.org/CVERecord?id=CVE-2026-64187 Référence CVE CVE-2026-64189 https://www.cve.org/CVERecord?id=CVE-2026-64189 Référence CVE CVE-2026-64191 https://www.cve.org/CVERecord?id=CVE-2026-64191 Référence CVE CVE-2026-64220 https://www.cve.org/CVERecord?id=CVE-2026-64220 Référence CVE CVE-2026-64221 https://www.cve.org/CVERecord?id=CVE-2026-64221 Référence CVE CVE-2026-64223 https://www.cve.org/CVERecord?id=CVE-2026-64223 Référence CVE CVE-2026-64231 https://www.cve.org/CVERecord?id=CVE-2026-64231 Référence CVE CVE-2026-64234 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-64174 Référence CVE CVE-2026-64175 https://www.cve.org/CVERecord?id=CVE-2026-64175 Référence CVE CVE-2026-64176 https://www.cve.org/CVERecord?id=CVE-2026-64176 Référence CVE CVE-2026-64177 https://www.cve.org/CVERecord?id=CVE-2026-64177 Référence CVE CVE-2026-64178 https://www.cve.org/CVERecord?id=CVE-2026-64178 Référence CVE CVE-2026-64179 https://www.cve.org/CVERecord?id=CVE-2026-64179 Référence CVE CVE-2026-64180 https://www.cve.org/CVERecord?id=CVE-2026-64180 Référence CVE CVE-2026-64181 https://www.cve.org/CVERecord?id=CVE-2026-64181 Référence CVE CVE-2026-64182 https://www.cve.org/CVERecord?id=CVE-2026-64182 Référence CVE CVE-2026-64183 https://www.cve.org/CVERecord?id=CVE-2026-64183 Référence CVE CVE-2026-64184 https://www.cve.org/CVERecord?id=CVE-2026-64184 Référence CVE CVE-2026-64185 https://www.cve.org/CVERecord?id=CVE-2026-64185 Référence CVE CVE-2026-64186 https://www.cve.org/CVERecord?id=CVE-2026-64186 Référence CVE CVE-2026-64208 https://www.cve.org/CVERecord?id=CVE-2026-64208 Référence CVE CVE-2026-64209 https://www.cve.org/CVERecord?id=CVE-2026-64209 Référence CVE CVE-2026-64210 https://www.cve.org/CVERecord?id=CVE-2026-64210 Référence CVE CVE-2026-64211 https://www.cve.org/CVERecord?id=CVE-2026-64211 Référence CVE CVE-2026-64212 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64025 Référence CVE CVE-2026-64034 https://www.cve.org/CVERecord?id=CVE-2026-64034 Référence CVE CVE-2026-64061 https://www.cve.org/CVERecord?id=CVE-2026-64061 Référence CVE CVE-2026-64091 https://www.cve.org/CVERecord?id=CVE-2026-64091 Référence CVE CVE-2026-64106 https://www.cve.org/CVERecord?id=CVE-2026-64106 Référence CVE CVE-2026-64157 https://www.cve.org/CVERecord?id=CVE-2026-64157 Référence CVE CVE-2026-64158 https://www.cve.org/CVERecord?id=CVE-2026-64158 Référence CVE CVE-2026-64174 https://www.cve.org/CVERecord?id=CVE-2026-64174 Référence CVE CVE-2026-64182 https://www.cve.org/CVERecord?id=CVE-2026-64182 Référence CVE CVE-2026-64183 https://www.cve.org/CVERecord?id=CVE-2026-64183 Référence CVE CVE-2026-64187 https://www.cve.org/CVERecord?id=CVE-2026-64187 Référence CVE CVE-2026-64188 https://www.cve.org/CVERecord?id=CVE-2026-64188 Référence CVE CVE-2026-64189 https://www.cve.org/CVERecord?id=CVE-2026-64189 Référence CVE CVE-2026-64191 https://www.cve.org/CVERecord?id=CVE-2026-64191 Référence CVE CVE-2026-64220 https://www.cve.org/CVERecord?id=CVE-2026-64220 Référence CVE CVE-2026-64221 https://www.cve.org/CVERecord?id=CVE-2026-64221 Référence CVE CVE-2026-64223 https://www.cve.org/CVERecord?id=CVE-2026-64223 Référence CVE CVE-2026-64231 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-64174 Référence CVE CVE-2026-64175 https://www.cve.org/CVERecord?id=CVE-2026-64175 Référence CVE CVE-2026-64176 https://www.cve.org/CVERecord?id=CVE-2026-64176 Référence CVE CVE-2026-64177 https://www.cve.org/CVERecord?id=CVE-2026-64177 Référence CVE CVE-2026-64178 https://www.cve.org/CVERecord?id=CVE-2026-64178 Référence CVE CVE-2026-64179 https://www.cve.org/CVERecord?id=CVE-2026-64179 Référence CVE CVE-2026-64180 https://www.cve.org/CVERecord?id=CVE-2026-64180 Référence CVE CVE-2026-64181 https://www.cve.org/CVERecord?id=CVE-2026-64181 Référence CVE CVE-2026-64182 https://www.cve.org/CVERecord?id=CVE-2026-64182 Référence CVE CVE-2026-64183 https://www.cve.org/CVERecord?id=CVE-2026-64183 Référence CVE CVE-2026-64184 https://www.cve.org/CVERecord?id=CVE-2026-64184 Référence CVE CVE-2026-64185 https://www.cve.org/CVERecord?id=CVE-2026-64185 Référence CVE CVE-2026-64186 https://www.cve.org/CVERecord?id=CVE-2026-64186 Référence CVE CVE-2026-64208 https://www.cve.org/CVERecord?id=CVE-2026-64208 Référence CVE CVE-2026-64209 https://www.cve.org/CVERecord?id=CVE-2026-64209 Référence CVE CVE-2026-64210 https://www.cve.org/CVERecord?id=CVE-2026-64210 Référence CVE CVE-2026-64211 https://www.cve.org/CVERecord?id=CVE-2026-64211 Référence CVE CVE-2026-64212 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-64174 Référence CVE CVE-2026-64175 https://www.cve.org/CVERecord?id=CVE-2026-64175 Référence CVE CVE-2026-64176 https://www.cve.org/CVERecord?id=CVE-2026-64176 Référence CVE CVE-2026-64177 https://www.cve.org/CVERecord?id=CVE-2026-64177 Référence CVE CVE-2026-64178 https://www.cve.org/CVERecord?id=CVE-2026-64178 Référence CVE CVE-2026-64179 https://www.cve.org/CVERecord?id=CVE-2026-64179 Référence CVE CVE-2026-64180 https://www.cve.org/CVERecord?id=CVE-2026-64180 Référence CVE CVE-2026-64181 https://www.cve.org/CVERecord?id=CVE-2026-64181 Référence CVE CVE-2026-64182 https://www.cve.org/CVERecord?id=CVE-2026-64182 Référence CVE CVE-2026-64183 https://www.cve.org/CVERecord?id=CVE-2026-64183 Référence CVE CVE-2026-64184 https://www.cve.org/CVERecord?id=CVE-2026-64184 Référence CVE CVE-2026-64185 https://www.cve.org/CVERecord?id=CVE-2026-64185 Référence CVE CVE-2026-64186 https://www.cve.org/CVERecord?id=CVE-2026-64186 Gestion détaillée du document le 24 juillet 2026 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-027878LinuxのLinux KernelにおけるNULL ポインタデリファレンスに関する脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました：efi: ACPI初期化前にランタイムワークキューを割り当てるコミット 5894cf571e14（"acpi/prmt: EFIランタイムサンドボックスを使用してPRMハンドラを呼び出す"）以降、ACPIのPRM呼び出しはカーネルスレッド内で動作するワークキューに委譲されており、ファームウェアによって行われる不正なメモリアクセスの検出および緩和が容易になっています。Rafaelの報告によると、このようなPRMアクセスはworkqueueが割り当てられるefisubsys_init()の実行前に発生する可能性があり、NULLポインタ参照を引き起こしていました。acpi_init()（初期のPRMアクセスをトリガーする関数）はsubsys_initcall()としても実行され、独自の依存関係があり、initcallの順序に影響を受けやすいため、acpi_init()の遅延は選択肢として適切ではありません。そこで、ワークキューの割り当てを独自のpostcore initcallに切り出しました。これがEFIランタイム呼び出しを可能にする唯一不足していた部分であり、これによりEFIランタイム呼び出し（PRM呼び出しを含む）がsubsys_initcall()レベルで動作するすべてのコードからアクセス可能になりました。

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: < 6.6, 6.6.142 ≤ 6.6.*, 6.12.92 ≤ 6.12.*, 6.18.34 ≤ 6.18.*, 7.0.11 ≤ 7.0.*, 7.1 ≤ *
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 19 Jul 2026 · Last source change 19 Jul 2026, 15:41 UTC · CWE-476 · NULL Pointer Dereference

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
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-45868
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
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-45868↗Vendor CSAF · SUSE Product Security Team↗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-64183 · cve.blacktree.nl