BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2024
CVE-2024-36478High confidence

null_blk: fix null-ptr-dereference while configuring 'power' and 'submit_queues'

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 61 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 11 May 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.27% 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 61 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.

17 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 13 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.9.7-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.119-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.9.7-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.9.7-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-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-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-oem-6.8Affected, 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-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
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-2024-36478 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: null_blk: fix null-ptr-dereference while configuring 'power' and 'submit_queues'
48 known affected

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

  • bpftool as a component of Red Hat Enterprise Linux 8
  • kernel as a component of Red Hat Enterprise Linux 8
  • kernel-abi-stablelists as a component of Red Hat Enterprise Linux 8
  • kernel-abi-whitelists as a component of Red Hat Enterprise Linux 8
  • kernel-core as a component of Red Hat Enterprise Linux 8
  • kernel-cross-headers as a component of Red Hat Enterprise Linux 8
  • kernel-debug as a component of Red Hat Enterprise Linux 8
  • kernel-debug-core as a component of Red Hat Enterprise Linux 8
  • kernel-debug-devel as a component of Red Hat Enterprise Linux 8
  • kernel-debug-modules as a component of Red Hat Enterprise Linux 8
  • kernel-debug-modules-extra as a component of Red Hat Enterprise Linux 8
  • kernel-debug-modules-internal as a component of Red Hat Enterprise Linux 8
Summary
In the Linux kernel, the following vulnerability has been resolved: null_blk: fix null-ptr-dereference while configuring 'power' and 'submit_queues' Writing 'power' and 'submit_queues' concurrently will trigger kernel panic: Test script: modprobe null_blk nr_devices=0 mkdir -p /sys/kernel/config/nullb/nullb0 while true; do echo 1 > submit_queues; echo 4 > submit_queues; done & while true; do echo 1 > power; echo 0 > power; done Test result: BUG: kernel NULL pointer dereference, address: 0000000000000148 Oops: 0000 [#1] PREEMPT SMP RIP: 0010:__lock_acquire+0x41d/0x28f0 Call Trace: lock_acquire+0x121/0x450 down_write+0x5f/0x1d0 simple_recursive_removal+0x12f/0x5c0 blk_mq_debugfs_unregister_hctxs+0x7c/0x100 blk_mq_update_nr_hw_queues+0x4a3/0x720 nullb_update_nr_hw_queues+0x71/0xf0 [null_blk] nullb_device_submit_queues_store+0x79/0xf0 [null_blk] configfs_write_iter+0x119/0x1e0 vfs_write+0x326/0x730 ksys_write+0x74/0x150 This is because del_gendisk() can concurrent with blk_mq_update_nr_hw_queues(): nullb_device_power_store nullb_apply_submit_queues null_del_dev del_gendisk nullb_update_nr_hw_queues if (!dev->nullb) // still set while gendisk is deleted return 0 blk_mq_update_nr_hw_queues dev->nullb = NULL Fix this problem by resuing the global mutex to protect nullb_device_power_store() and nullb_update_nr_hw_queues() from configfs.
Remediation
Fix deferred
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-2024-36256

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 61 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: null_blk: fix null-ptr-dereference while configuring 'power' and 'submit_queues' Writing 'power' and 'submit_queues' concurrently will trigger kernel panic: Test script: modprobe null_blk nr_devices=0 mkdir -p /sys/kernel/config/nullb/nullb0 while true; do echo 1 > submit_queues; echo 4 > submit_queues; done & while true; do echo 1 > power; echo 0 > power; done Test result: BUG: kernel NULL pointer dereference, address: 0000000000000148 Oops: 0000 [#1] PREEMPT SMP RIP: 0010:__lock_acquire+0x41d/0x28f0 Call Trace: <TASK> lock_acquire+0x121/0x450 down_write+0x5f/0x1d0 simple_recursive_removal+0x12f/0x5c0 blk_mq_debugfs_unregister_hctxs+0x7c/0x100 blk_mq_update_nr_hw_queues+0x4a3/0x720 nullb_update_nr_hw_queues+0x71/0xf0 [null_blk] nullb_device_submit_queues_store+0x79/0xf0 [null_blk] configfs_write_iter+0x119/0x1e0 vfs_write+0x326/0x730 ksys_write+0x74/0x150 This is because del_gendisk() can concurrent with blk_mq_update_nr_hw_queues(): nullb_device_power_store nullb_apply_submit_queues null_del_dev del_gendisk nullb_update_nr_hw_queues if (!dev->nullb) // still set while gendisk is deleted return 0 blk_mq_update_nr_hw_queues dev->nullb = NULL Fix this problem by resuing the global mutex to protect nullb_device_power_store() and nullb_update_nr_hw_queues() from configfs.

What

In the Linux kernel, the following vulnerability has been resolved: null_blk: fix null-ptr-dereference while configuring 'power' and 'submit_queues' Writing 'power' and 'submit_queues' concurrently will trigger kernel panic: Test script: modprobe null_blk nr_devices=0 mkdir -p /sys/kernel/config/nullb/nullb0 while true; do echo 1 > submit_queues; echo 4 > submit_queues; done & while true; do echo 1 > power; echo 0 > power; done Test result: BUG: kernel NULL pointer dereference, address: 0000000000000148 Oops: 0000 [#1] PREEMPT SMP RIP: 0010:__lock_acquire+0x41d/0x28f0 Call Trace: <TASK> lock_acquire+0x121/0x450 down_write+0x5f/0x1d0 simple_recursive_removal+0x12f/0x5c0 blk_mq_debugfs_unregister_hctxs+0x7c/0x100 blk_mq_update_nr_hw_queues+0x4a3/0x720 nullb_update_nr_hw_queues+0x71/0xf0 [null_blk] nullb_device_submit_queues_store+0x79/0xf0 [null_blk] configfs_write_iter+0x119/0x1e0 vfs_write+0x326/0x730 ksys_write+0x74/0x150 This is because del_gendisk() can concurrent with blk_mq_update_nr_hw_queues(): nullb_device_power_store nullb_apply_submit_queues null_del_dev del_gendisk nullb_update_nr_hw_queues if (!dev->nullb) // still set while gendisk is deleted return 0 blk_mq_update_nr_hw_queues dev->nullb = NULL Fix this problem by resuing the global mutex to protect nullb_device_power_store() and nullb_update_nr_hw_queues() from configfs.

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: null_blk: fix null-ptr-dereference while configuring 'power' and 'submit_queues' Writing 'power' and 'submit_queues' concurrently will trigger kernel panic: Test script: modprobe null_blk nr_devices=0 mkdir -p /sys/kernel/config/nullb/nullb0 while true; do echo 1 > submit_queues; echo 4 > submit_queues; done & while true; do echo 1 > power; echo 0 > power; done Test result: BUG: kernel NULL pointer dereference, address: 0000000000000148 Oops: 0000 [#1] PREEMPT SMP RIP: 0010:__lock_acquire+0x41d/0x28f0 Call Trace: <TASK> lock_acquire+0x121/0x450 down_write+0x5f/0x1d0 simple_recursive_removal+0x12f/0x5c0 blk_mq_debugfs_unregister_hctxs+0x7c/0x100 blk_mq_update_nr_hw_queues+0x4a3/0x720 nullb_update_nr_hw_queues+0x71/0xf0 [null_blk] nullb_device_submit_queues_store+0x79/0xf0 [null_blk] configfs_write_iter+0x119/0x1e0 vfs_write+0x326/0x730 ksys_write+0x74/0x150 This is because del_gendisk() can concurrent with blk_mq_update_nr_hw_queues(): nullb_device_power_store nullb_apply_submit_queues null_del_dev del_gendisk nullb_update_nr_hw_queues if (!dev->nullb) // still set while gendisk is deleted return 0 blk_mq_update_nr_hw_queues dev->nullb = NULL Fix this problem by resuing the global mutex to protect nullb_device_power_store() and nullb_update_nr_hw_queues() from configfs.

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-2024-1422Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20240626Security Bulletin 26 Jun 2024

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 26 Jun 2024, published on 26 June 2024. Open the linked bulletin for the product, severity and reference information published in that issue.

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

d?id=CVE-2024-36013 Référence CVE CVE-2024-36021 https://www.cve.org/CVERecord?id=CVE-2024-36021 Référence CVE CVE-2024-36024 https://www.cve.org/CVERecord?id=CVE-2024-36024 Référence CVE CVE-2024-36026 https://www.cve.org/CVERecord?id=CVE-2024-36026 Référence CVE CVE-2024-36244 https://www.cve.org/CVERecord?id=CVE-2024-36244 Référence CVE CVE-2024-36331 https://www.cve.org/CVERecord?id=CVE-2024-36331 Référence CVE CVE-2024-36347 https://www.cve.org/CVERecord?id=CVE-2024-36347 Référence CVE CVE-2024-36350 https://www.cve.org/CVERecord?id=CVE-2024-36350 Référence CVE CVE-2024-36357 https://www.cve.org/CVERecord?id=CVE-2024-36357 Référence CVE CVE-2024-36478 https://www.cve.org/CVERecord?id=CVE-2024-36478 Référence CVE CVE-2024-36479 https://www.cve.org/CVERecord?id=CVE-2024-36479 Référence CVE CVE-2024-3651 https://www.cve.org/CVERecord?id=CVE-2024-3651 Référence CVE CVE-2024-36898 https://www.cve.org/CVERecord?id=CVE-2024-36898 Référence CVE CVE-2024-36900 https://www.cve.org/CVERecord?id=CVE-2024-36900 Référence CVE CVE-2024-36903 https://www.cve.org/CVERecord?id=CVE-2024-36903 Référence CVE CVE-2024-36909 https://www.cve.org/CVERecord?id=CVE-2024-36909 Référence CVE CVE-2024-36910 https://www.cve.org/CVERecord?id=CVE-2024-36910 Référence CVE CVE-2024-36911 https://www.cve.org/CVERecord?id=CV

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

d?id=CVE-2024-36013 Référence CVE CVE-2024-36021 https://www.cve.org/CVERecord?id=CVE-2024-36021 Référence CVE CVE-2024-36024 https://www.cve.org/CVERecord?id=CVE-2024-36024 Référence CVE CVE-2024-36026 https://www.cve.org/CVERecord?id=CVE-2024-36026 Référence CVE CVE-2024-36244 https://www.cve.org/CVERecord?id=CVE-2024-36244 Référence CVE CVE-2024-36331 https://www.cve.org/CVERecord?id=CVE-2024-36331 Référence CVE CVE-2024-36347 https://www.cve.org/CVERecord?id=CVE-2024-36347 Référence CVE CVE-2024-36350 https://www.cve.org/CVERecord?id=CVE-2024-36350 Référence CVE CVE-2024-36357 https://www.cve.org/CVERecord?id=CVE-2024-36357 Référence CVE CVE-2024-36478 https://www.cve.org/CVERecord?id=CVE-2024-36478 Référence CVE CVE-2024-36479 https://www.cve.org/CVERecord?id=CVE-2024-36479 Référence CVE CVE-2024-3651 https://www.cve.org/CVERecord?id=CVE-2024-3651 Référence CVE CVE-2024-36898 https://www.cve.org/CVERecord?id=CVE-2024-36898 Référence CVE CVE-2024-36900 https://www.cve.org/CVERecord?id=CVE-2024-36900 Référence CVE CVE-2024-36903 https://www.cve.org/CVERecord?id=CVE-2024-36903 Référence CVE CVE-2024-36909 https://www.cve.org/CVERecord?id=CVE-2024-36909 Référence CVE CVE-2024-36910 https://www.cve.org/CVERecord?id=CVE-2024-36910 Référence CVE CVE-2024-36911 https://www.cve.org/CVERecord?id=CV

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

d?id=CVE-2024-27017 Référence CVE CVE-2024-27072 https://www.cve.org/CVERecord?id=CVE-2024-27072 Référence CVE CVE-2024-27397 https://www.cve.org/CVERecord?id=CVE-2024-27397 Référence CVE CVE-2024-35937 https://www.cve.org/CVERecord?id=CVE-2024-35937 Référence CVE CVE-2024-35943 https://www.cve.org/CVERecord?id=CVE-2024-35943 Référence CVE CVE-2024-35963 https://www.cve.org/CVERecord?id=CVE-2024-35963 Référence CVE CVE-2024-35964 https://www.cve.org/CVERecord?id=CVE-2024-35964 Référence CVE CVE-2024-35966 https://www.cve.org/CVERecord?id=CVE-2024-35966 Référence CVE CVE-2024-36244 https://www.cve.org/CVERecord?id=CVE-2024-36244 Référence CVE CVE-2024-36478 https://www.cve.org/CVERecord?id=CVE-2024-36478 Référence CVE CVE-2024-36894 https://www.cve.org/CVERecord?id=CVE-2024-36894 Référence CVE CVE-2024-36914 https://www.cve.org/CVERecord?id=CVE-2024-36914 Référence CVE CVE-2024-36915 https://www.cve.org/CVERecord?id=CVE-2024-36915 Référence CVE CVE-2024-36923 https://www.cve.org/CVERecord?id=CVE-2024-36923 Référence CVE CVE-2024-36973 https://www.cve.org/CVERecord?id=CVE-2024-36973 Référence CVE CVE-2024-36978 https://www.cve.org/CVERecord?id=CVE-2024-36978 Référence CVE CVE-2024-37078 https://www.cve.org/CVERecord?id=CVE-2024-37078 Référence CVE CVE-2024-38540 https://www.cve.org/CVERecord?id=

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

fs (cf. section Documentation). Documentation Bulletin de sécurité Debian DSA-5818-1 du 24 novembre 2024 https://lists.debian.org/debian-security-announce/2024/msg00233.html Référence CVE CVE-2022-45888 https://www.cve.org/CVERecord?id=CVE-2022-45888 Référence CVE CVE-2023-52812 https://www.cve.org/CVERecord?id=CVE-2023-52812 Référence CVE CVE-2024-26952 https://www.cve.org/CVERecord?id=CVE-2024-26952 Référence CVE CVE-2024-26954 https://www.cve.org/CVERecord?id=CVE-2024-26954 Référence CVE CVE-2024-35964 https://www.cve.org/CVERecord?id=CVE-2024-35964 Référence CVE CVE-2024-36244 https://www.cve.org/CVERecord?id=CVE-2024-36244 Référence CVE CVE-2024-36478 https://www.cve.org/CVERecord?id=CVE-2024-36478 Référence CVE CVE-2024-36914 https://www.cve.org/CVERecord?id=CVE-2024-36914 Référence CVE CVE-2024-36915 https://www.cve.org/CVERecord?id=CVE-2024-36915 Référence CVE CVE-2024-36923 https://www.cve.org/CVERecord?id=CVE-2024-36923 Référence CVE CVE-2024-38540 https://www.cve.org/CVERecord?id=CVE-2024-38540 Référence CVE CVE-2024-38553 https://www.cve.org/CVERecord?id=CVE-2024-38553 Référence CVE CVE-2024-41080 https://www.cve.org/CVERecord?id=CVE-2024-41080 Référence CVE CVE-2024-42322 https://www.cve.org/CVERecord?id=CVE-2024-42322 Référence CVE CVE-2024-43868 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-36014 Référence CVE CVE-2024-36015 https://www.cve.org/CVERecord?id=CVE-2024-36015 Référence CVE CVE-2024-36032 https://www.cve.org/CVERecord?id=CVE-2024-36032 Référence CVE CVE-2024-36244 https://www.cve.org/CVERecord?id=CVE-2024-36244 Référence CVE CVE-2024-36270 https://www.cve.org/CVERecord?id=CVE-2024-36270 Référence CVE CVE-2024-36281 https://www.cve.org/CVERecord?id=CVE-2024-36281 Référence CVE CVE-2024-36286 https://www.cve.org/CVERecord?id=CVE-2024-36286 Référence CVE CVE-2024-36288 https://www.cve.org/CVERecord?id=CVE-2024-36288 Référence CVE CVE-2024-36477 https://www.cve.org/CVERecord?id=CVE-2024-36477 Référence CVE CVE-2024-36478 https://www.cve.org/CVERecord?id=CVE-2024-36478 Référence CVE CVE-2024-36479 https://www.cve.org/CVERecord?id=CVE-2024-36479 Référence CVE CVE-2024-36481 https://www.cve.org/CVERecord?id=CVE-2024-36481 Référence CVE CVE-2024-36484 https://www.cve.org/CVERecord?id=CVE-2024-36484 Référence CVE CVE-2024-36489 https://www.cve.org/CVERecord?id=CVE-2024-36489 Référence CVE CVE-2024-36894 https://www.cve.org/CVERecord?id=CVE-2024-36894 Référence CVE CVE-2024-36971 https://www.cve.org/CVERecord?id=CVE-2024-36971 Référence CVE CVE-2024-36972 https://www.cve.org/CVERecord?id=CVE-2024-36972 Référence CVE CVE-2024-36973 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-36025 Référence CVE CVE-2024-36029 https://www.cve.org/CVERecord?id=CVE-2024-36029 Référence CVE CVE-2024-36031 https://www.cve.org/CVERecord?id=CVE-2024-36031 Référence CVE CVE-2024-36032 https://www.cve.org/CVERecord?id=CVE-2024-36032 Référence CVE CVE-2024-36244 https://www.cve.org/CVERecord?id=CVE-2024-36244 Référence CVE CVE-2024-36270 https://www.cve.org/CVERecord?id=CVE-2024-36270 Référence CVE CVE-2024-36281 https://www.cve.org/CVERecord?id=CVE-2024-36281 Référence CVE CVE-2024-36286 https://www.cve.org/CVERecord?id=CVE-2024-36286 Référence CVE CVE-2024-36288 https://www.cve.org/CVERecord?id=CVE-2024-36288 Référence CVE CVE-2024-36478 https://www.cve.org/CVERecord?id=CVE-2024-36478 Référence CVE CVE-2024-36479 https://www.cve.org/CVERecord?id=CVE-2024-36479 Référence CVE CVE-2024-36481 https://www.cve.org/CVERecord?id=CVE-2024-36481 Référence CVE CVE-2024-36484 https://www.cve.org/CVERecord?id=CVE-2024-36484 Référence CVE CVE-2024-36489 https://www.cve.org/CVERecord?id=CVE-2024-36489 Référence CVE CVE-2024-36880 https://www.cve.org/CVERecord?id=CVE-2024-36880 Référence CVE CVE-2024-36883 https://www.cve.org/CVERecord?id=CVE-2024-36883 Référence CVE CVE-2024-36886 https://www.cve.org/CVERecord?id=CVE-2024-36886 Référence CVE CVE-2024-36889 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-36014 Référence CVE CVE-2024-36015 https://www.cve.org/CVERecord?id=CVE-2024-36015 Référence CVE CVE-2024-36032 https://www.cve.org/CVERecord?id=CVE-2024-36032 Référence CVE CVE-2024-36244 https://www.cve.org/CVERecord?id=CVE-2024-36244 Référence CVE CVE-2024-36270 https://www.cve.org/CVERecord?id=CVE-2024-36270 Référence CVE CVE-2024-36281 https://www.cve.org/CVERecord?id=CVE-2024-36281 Référence CVE CVE-2024-36286 https://www.cve.org/CVERecord?id=CVE-2024-36286 Référence CVE CVE-2024-36288 https://www.cve.org/CVERecord?id=CVE-2024-36288 Référence CVE CVE-2024-36477 https://www.cve.org/CVERecord?id=CVE-2024-36477 Référence CVE CVE-2024-36478 https://www.cve.org/CVERecord?id=CVE-2024-36478 Référence CVE CVE-2024-36479 https://www.cve.org/CVERecord?id=CVE-2024-36479 Référence CVE CVE-2024-36481 https://www.cve.org/CVERecord?id=CVE-2024-36481 Référence CVE CVE-2024-36484 https://www.cve.org/CVERecord?id=CVE-2024-36484 Référence CVE CVE-2024-36489 https://www.cve.org/CVERecord?id=CVE-2024-36489 Référence CVE CVE-2024-36894 https://www.cve.org/CVERecord?id=CVE-2024-36894 Référence CVE CVE-2024-36901 https://www.cve.org/CVERecord?id=CVE-2024-36901 Référence CVE CVE-2024-36971 https://www.cve.org/CVERecord?id=CVE-2024-36971 Référence CVE CVE-2024-36972 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-36024 Référence CVE CVE-2024-36025 https://www.cve.org/CVERecord?id=CVE-2024-36025 Référence CVE CVE-2024-36026 https://www.cve.org/CVERecord?id=CVE-2024-36026 Référence CVE CVE-2024-36029 https://www.cve.org/CVERecord?id=CVE-2024-36029 Référence CVE CVE-2024-36030 https://www.cve.org/CVERecord?id=CVE-2024-36030 Référence CVE CVE-2024-36032 https://www.cve.org/CVERecord?id=CVE-2024-36032 Référence CVE CVE-2024-36281 https://www.cve.org/CVERecord?id=CVE-2024-36281 Référence CVE CVE-2024-36288 https://www.cve.org/CVERecord?id=CVE-2024-36288 Référence CVE CVE-2024-36477 https://www.cve.org/CVERecord?id=CVE-2024-36477 Référence CVE CVE-2024-36478 https://www.cve.org/CVERecord?id=CVE-2024-36478 Référence CVE CVE-2024-36479 https://www.cve.org/CVERecord?id=CVE-2024-36479 Référence CVE CVE-2024-36592 https://www.cve.org/CVERecord?id=CVE-2024-36592 Référence CVE CVE-2024-36880 https://www.cve.org/CVERecord?id=CVE-2024-36880 Référence CVE CVE-2024-36882 https://www.cve.org/CVERecord?id=CVE-2024-36882 Référence CVE CVE-2024-36885 https://www.cve.org/CVERecord?id=CVE-2024-36885 Référence CVE CVE-2024-36887 https://www.cve.org/CVERecord?id=CVE-2024-36887 Référence CVE CVE-2024-36889 https://www.cve.org/CVERecord?id=CVE-2024-36889 Référence CVE CVE-2024-36890 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-36014 Référence CVE CVE-2024-36017 https://www.cve.org/CVERecord?id=CVE-2024-36017 Référence CVE CVE-2024-36020 https://www.cve.org/CVERecord?id=CVE-2024-36020 Référence CVE CVE-2024-36021 https://www.cve.org/CVERecord?id=CVE-2024-36021 Référence CVE CVE-2024-36024 https://www.cve.org/CVERecord?id=CVE-2024-36024 Référence CVE CVE-2024-36025 https://www.cve.org/CVERecord?id=CVE-2024-36025 Référence CVE CVE-2024-36281 https://www.cve.org/CVERecord?id=CVE-2024-36281 Référence CVE CVE-2024-36288 https://www.cve.org/CVERecord?id=CVE-2024-36288 Référence CVE CVE-2024-36477 https://www.cve.org/CVERecord?id=CVE-2024-36477 Référence CVE CVE-2024-36478 https://www.cve.org/CVERecord?id=CVE-2024-36478 Référence CVE CVE-2024-36479 https://www.cve.org/CVERecord?id=CVE-2024-36479 Référence CVE CVE-2024-36592 https://www.cve.org/CVERecord?id=CVE-2024-36592 Référence CVE CVE-2024-36882 https://www.cve.org/CVERecord?id=CVE-2024-36882 Référence CVE CVE-2024-36887 https://www.cve.org/CVERecord?id=CVE-2024-36887 Référence CVE CVE-2024-36889 https://www.cve.org/CVERecord?id=CVE-2024-36889 Référence CVE CVE-2024-36890 https://www.cve.org/CVERecord?id=CVE-2024-36890 Référence CVE CVE-2024-36894 https://www.cve.org/CVERecord?id=CVE-2024-36894 Référence CVE CVE-2024-36899 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-35979 Référence CVE CVE-2024-35998 https://www.cve.org/CVERecord?id=CVE-2024-35998 Référence CVE CVE-2024-36005 https://www.cve.org/CVERecord?id=CVE-2024-36005 Référence CVE CVE-2024-36008 https://www.cve.org/CVERecord?id=CVE-2024-36008 Référence CVE CVE-2024-36010 https://www.cve.org/CVERecord?id=CVE-2024-36010 Référence CVE CVE-2024-36017 https://www.cve.org/CVERecord?id=CVE-2024-36017 Référence CVE CVE-2024-36024 https://www.cve.org/CVERecord?id=CVE-2024-36024 Référence CVE CVE-2024-36281 https://www.cve.org/CVERecord?id=CVE-2024-36281 Référence CVE CVE-2024-36477 https://www.cve.org/CVERecord?id=CVE-2024-36477 Référence CVE CVE-2024-36478 https://www.cve.org/CVERecord?id=CVE-2024-36478 Référence CVE CVE-2024-36479 https://www.cve.org/CVERecord?id=CVE-2024-36479 Référence CVE CVE-2024-36882 https://www.cve.org/CVERecord?id=CVE-2024-36882 Référence CVE CVE-2024-36887 https://www.cve.org/CVERecord?id=CVE-2024-36887 Référence CVE CVE-2024-36899 https://www.cve.org/CVERecord?id=CVE-2024-36899 Référence CVE CVE-2024-36900 https://www.cve.org/CVERecord?id=CVE-2024-36900 Référence CVE CVE-2024-36903 https://www.cve.org/CVERecord?id=CVE-2024-36903 Référence CVE CVE-2024-36904 https://www.cve.org/CVERecord?id=CVE-2024-36904 Référence CVE CVE-2024-36915 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-35998 Référence CVE CVE-2024-36005 https://www.cve.org/CVERecord?id=CVE-2024-36005 Référence CVE CVE-2024-36008 https://www.cve.org/CVERecord?id=CVE-2024-36008 Référence CVE CVE-2024-36016 https://www.cve.org/CVERecord?id=CVE-2024-36016 Référence CVE CVE-2024-36017 https://www.cve.org/CVERecord?id=CVE-2024-36017 Référence CVE CVE-2024-36020 https://www.cve.org/CVERecord?id=CVE-2024-36020 Référence CVE CVE-2024-36021 https://www.cve.org/CVERecord?id=CVE-2024-36021 Référence CVE CVE-2024-36025 https://www.cve.org/CVERecord?id=CVE-2024-36025 Référence CVE CVE-2024-36477 https://www.cve.org/CVERecord?id=CVE-2024-36477 Référence CVE CVE-2024-36478 https://www.cve.org/CVERecord?id=CVE-2024-36478 Référence CVE CVE-2024-36479 https://www.cve.org/CVERecord?id=CVE-2024-36479 Référence CVE CVE-2024-36592 https://www.cve.org/CVERecord?id=CVE-2024-36592 Référence CVE CVE-2024-36880 https://www.cve.org/CVERecord?id=CVE-2024-36880 Référence CVE CVE-2024-36890 https://www.cve.org/CVERecord?id=CVE-2024-36890 Référence CVE CVE-2024-36894 https://www.cve.org/CVERecord?id=CVE-2024-36894 Référence CVE CVE-2024-36899 https://www.cve.org/CVERecord?id=CVE-2024-36899 Référence CVE CVE-2024-36900 https://www.cve.org/CVERecord?id=CVE-2024-36900 Référence CVE CVE-2024-36904 https://www.cve.org/CVERecord?id=

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

Linux の Linux Kernel には、NULL ポインタデリファレンスに関する脆弱性が存在します。

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.5, 6.1.119 ≤ 6.1.*, 6.6.55 ≤ 6.6.*, 6.9.4 ≤ 6.9.*, 6.10 ≤ *
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 21 Jun 2024 · Last source change 11 May 2026, 20:16 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-2024-36256
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

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-2024-36256↗Vendor CSAF · Red Hat Product Security↗Patch or update reference↗Patch or update reference↗CVE authority or vendor 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-2024-36478 · cve.blacktree.nl