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

fpga: region: add owner module and take its refcount

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 15 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.23% 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 15 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 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.94-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.9.7-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.9.7-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-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.

2 current
CVE-2024-35247 · CSAF 2.0 · revision 93 · interimSUSE Product Security TeamCVE-2024-35247
307 known affected

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

  • kernel-default as component of SUSE Enterprise Storage 7.1
  • kernel-default-devel as component of SUSE Enterprise Storage 7.1
  • kernel-devel as component of SUSE Enterprise Storage 7.1
  • kernel-macros as component of SUSE Enterprise Storage 7.1
  • kernel-source as component of SUSE Enterprise Storage 7.1
  • reiserfs-kmp-default as component of SUSE Enterprise Storage 7.1
  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-default-devel as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-devel as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-macros as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP4
Summary
In the Linux kernel, the following vulnerability has been resolved: fpga: region: add owner module and take its refcount The current implementation of the fpga region assumes that the low-level module registers a driver for the parent device and uses its owner pointer to take the module's refcount. This approach is problematic since it can lead to a null pointer dereference while attempting to get the region during programming if the parent device does not have a driver. To address this problem, add a module owner pointer to the fpga_region struct and use it to take the module's refcount. Modify the functions for registering a region to take an additional owner module parameter and rename them to avoid conflicts. Use the old function names for helper macros that automatically set the module that registers the region as the owner. This ensures compatibility with existing low-level control modules and reduces the chances of registering a region without setting the owner. Also, update the documentation to keep it consistent with the new interface for registering an fpga region.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
SSA-613116 · CSAF 2.0 · revision 3 · interimSiemens ProductCERTSSA-613116: Multiple Vulnerabilities in Third-Party Components in SINEC OS before V3.1
2 known affected

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

  • RUGGEDCOM RST2428P (6GK6242-6PA00)
  • SCALANCE XCM-/XRM-/XCH-/XRH-300 family
Summary
In the Linux kernel, the following vulnerability has been resolved: fpga: region: add owner module and take its refcount The current implementation of the fpga region assumes that the low-level module registers a driver for the parent device and uses its owner pointer to take the module's refcount. This approach is problematic since it can lead to a null pointer dereference while attempting to get the region during programming if the parent device does not have a driver. To address this problem, add a module owner pointer to the fpga_region struct and use it to take the module's refcount. Modify the functions for registering a region to take an additional owner module parameter and rename them to avoid conflicts. Use the old function names for helper macros that automatically set the module that registers the region as the owner. This ensures compatibility with existing low-level control modules and reduces the chances of registering a region without setting the owner. Also, update the documentation to keep it consistent with the new interface for registering an fpga region.
Remediation
Update to V3.1 or later version
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-35758

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 15 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: fpga: region: add owner module and take its refcount The current implementation of the fpga region assumes that the low-level module registers a driver for the parent device and uses its owner pointer to take the module's refcount. This approach is problematic since it can lead to a null pointer dereference while attempting to get the region during programming if the parent device does not have a driver. To address this problem, add a module owner pointer to the fpga_region struct and use it to take the module's refcount. Modify the functions for registering a region to take an additional owner module parameter and rename them to avoid conflicts. Use the old function names for helper macros that automatically set the module that registers the region as the owner. This ensures compatibility with existing low-level control modules and reduces the chances of registering a region without setting the owner. Also, update the documentation to keep it consistent with the new interface for registering an fpga region.

What

In the Linux kernel, the following vulnerability has been resolved: fpga: region: add owner module and take its refcount The current implementation of the fpga region assumes that the low-level module registers a driver for the parent device and uses its owner pointer to take the module's refcount. This approach is problematic since it can lead to a null pointer dereference while attempting to get the region during programming if the parent device does not have a driver. To address this problem, add a module owner pointer to the fpga_region struct and use it to take the module's refcount. Modify the functions for registering a region to take an additional owner module parameter and rename them to avoid conflicts. Use the old function names for helper macros that automatically set the module that registers the region as the owner. This ensures compatibility with existing low-level control modules and reduces the chances of registering a region without setting the owner. Also, update the documentation to keep it consistent with the new interface for registering an fpga region.

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: fpga: region: add owner module and take its refcount The current implementation of the fpga region assumes that the low-level module registers a driver for the parent device and uses its owner pointer to take the module's refcount. This approach is problematic since it can lead to a null pointer dereference while attempting to get the region during programming if the parent device does not have a driver. To address this problem, add a module owner pointer to the fpga_region struct and use it to take the module's refcount. Modify the functions for registering a region to take an additional owner module parameter and rename them to avoid conflicts. Use the old function names for helper macros that automatically set the module that registers the region as the owner. This ensures compatibility with existing low-level control modules and reduces the chances of registering a region without setting the owner. Also, update the documentation to keep it consistent with the new interface for registering an fpga region.

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-1443Linux 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-2024-AVI-0823Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2024-27437 Référence CVE CVE-2024-31076 https://www.cve.org/CVERecord?id=CVE-2024-31076 Référence CVE CVE-2024-32936 https://www.cve.org/CVERecord?id=CVE-2024-32936 Référence CVE CVE-2024-33619 https://www.cve.org/CVERecord?id=CVE-2024-33619 Référence CVE CVE-2024-33621 https://www.cve.org/CVERecord?id=CVE-2024-33621 Référence CVE CVE-2024-33847 https://www.cve.org/CVERecord?id=CVE-2024-33847 Référence CVE CVE-2024-34027 https://www.cve.org/CVERecord?id=CVE-2024-34027 Référence CVE CVE-2024-34030 https://www.cve.org/CVERecord?id=CVE-2024-34030 Référence CVE CVE-2024-34777 https://www.cve.org/CVERecord?id=CVE-2024-34777 Référence CVE CVE-2024-35247 https://www.cve.org/CVERecord?id=CVE-2024-35247 Référence CVE CVE-2024-35927 https://www.cve.org/CVERecord?id=CVE-2024-35927 Référence CVE CVE-2024-36014 https://www.cve.org/CVERecord?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=

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

d?id=CVE-2024-27437 Référence CVE CVE-2024-31076 https://www.cve.org/CVERecord?id=CVE-2024-31076 Référence CVE CVE-2024-32936 https://www.cve.org/CVERecord?id=CVE-2024-32936 Référence CVE CVE-2024-33619 https://www.cve.org/CVERecord?id=CVE-2024-33619 Référence CVE CVE-2024-33621 https://www.cve.org/CVERecord?id=CVE-2024-33621 Référence CVE CVE-2024-33847 https://www.cve.org/CVERecord?id=CVE-2024-33847 Référence CVE CVE-2024-34027 https://www.cve.org/CVERecord?id=CVE-2024-34027 Référence CVE CVE-2024-34030 https://www.cve.org/CVERecord?id=CVE-2024-34030 Référence CVE CVE-2024-34777 https://www.cve.org/CVERecord?id=CVE-2024-34777 Référence CVE CVE-2024-35247 https://www.cve.org/CVERecord?id=CVE-2024-35247 Référence CVE CVE-2024-35785 https://www.cve.org/CVERecord?id=CVE-2024-35785 Référence CVE CVE-2024-35789 https://www.cve.org/CVERecord?id=CVE-2024-35789 Référence CVE CVE-2024-35791 https://www.cve.org/CVERecord?id=CVE-2024-35791 Référence CVE CVE-2024-35796 https://www.cve.org/CVERecord?id=CVE-2024-35796 Référence CVE CVE-2024-35804 https://www.cve.org/CVERecord?id=CVE-2024-35804 Référence CVE CVE-2024-35805 https://www.cve.org/CVERecord?id=CVE-2024-35805 Référence CVE CVE-2024-35806 https://www.cve.org/CVERecord?id=CVE-2024-35806 Référence CVE CVE-2024-35807 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-26929 Référence CVE CVE-2024-31076 https://www.cve.org/CVERecord?id=CVE-2024-31076 Référence CVE CVE-2024-32936 https://www.cve.org/CVERecord?id=CVE-2024-32936 Référence CVE CVE-2024-33619 https://www.cve.org/CVERecord?id=CVE-2024-33619 Référence CVE CVE-2024-33621 https://www.cve.org/CVERecord?id=CVE-2024-33621 Référence CVE CVE-2024-33847 https://www.cve.org/CVERecord?id=CVE-2024-33847 Référence CVE CVE-2024-34027 https://www.cve.org/CVERecord?id=CVE-2024-34027 Référence CVE CVE-2024-34030 https://www.cve.org/CVERecord?id=CVE-2024-34030 Référence CVE CVE-2024-34777 https://www.cve.org/CVERecord?id=CVE-2024-34777 Référence CVE CVE-2024-35247 https://www.cve.org/CVERecord?id=CVE-2024-35247 Référence CVE CVE-2024-35927 https://www.cve.org/CVERecord?id=CVE-2024-35927 Référence CVE CVE-2024-36014 https://www.cve.org/CVERecord?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=

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

d?id=CVE-2024-27419 Référence CVE CVE-2024-27431 https://www.cve.org/CVERecord?id=CVE-2024-27431 Référence CVE CVE-2024-27432 https://www.cve.org/CVERecord?id=CVE-2024-27432 Référence CVE CVE-2024-27434 https://www.cve.org/CVERecord?id=CVE-2024-27434 Référence CVE CVE-2024-27435 https://www.cve.org/CVERecord?id=CVE-2024-27435 Référence CVE CVE-2024-27436 https://www.cve.org/CVERecord?id=CVE-2024-27436 Référence CVE CVE-2024-27437 https://www.cve.org/CVERecord?id=CVE-2024-27437 Référence CVE CVE-2024-33619 https://www.cve.org/CVERecord?id=CVE-2024-33619 Référence CVE CVE-2024-34777 https://www.cve.org/CVERecord?id=CVE-2024-34777 Référence CVE CVE-2024-35247 https://www.cve.org/CVERecord?id=CVE-2024-35247 Référence CVE CVE-2024-35784 https://www.cve.org/CVERecord?id=CVE-2024-35784 Référence CVE CVE-2024-35786 https://www.cve.org/CVERecord?id=CVE-2024-35786 Référence CVE CVE-2024-35788 https://www.cve.org/CVERecord?id=CVE-2024-35788 Référence CVE CVE-2024-35789 https://www.cve.org/CVERecord?id=CVE-2024-35789 Référence CVE CVE-2024-35790 https://www.cve.org/CVERecord?id=CVE-2024-35790 Référence CVE CVE-2024-35791 https://www.cve.org/CVERecord?id=CVE-2024-35791 Référence CVE CVE-2024-35794 https://www.cve.org/CVERecord?id=CVE-2024-35794 Référence CVE CVE-2024-35795 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-27398 Référence CVE CVE-2024-27402 https://www.cve.org/CVERecord?id=CVE-2024-27402 Référence CVE CVE-2024-27404 https://www.cve.org/CVERecord?id=CVE-2024-27404 Référence CVE CVE-2024-27414 https://www.cve.org/CVERecord?id=CVE-2024-27414 Référence CVE CVE-2024-27419 https://www.cve.org/CVERecord?id=CVE-2024-27419 Référence CVE CVE-2024-27432 https://www.cve.org/CVERecord?id=CVE-2024-27432 Référence CVE CVE-2024-27437 https://www.cve.org/CVERecord?id=CVE-2024-27437 Référence CVE CVE-2024-33619 https://www.cve.org/CVERecord?id=CVE-2024-33619 Référence CVE CVE-2024-34777 https://www.cve.org/CVERecord?id=CVE-2024-34777 Référence CVE CVE-2024-35247 https://www.cve.org/CVERecord?id=CVE-2024-35247 Référence CVE CVE-2024-35789 https://www.cve.org/CVERecord?id=CVE-2024-35789 Référence CVE CVE-2024-35790 https://www.cve.org/CVERecord?id=CVE-2024-35790 Référence CVE CVE-2024-35805 https://www.cve.org/CVERecord?id=CVE-2024-35805 Référence CVE CVE-2024-35806 https://www.cve.org/CVERecord?id=CVE-2024-35806 Référence CVE CVE-2024-35807 https://www.cve.org/CVERecord?id=CVE-2024-35807 Référence CVE CVE-2024-35814 https://www.cve.org/CVERecord?id=CVE-2024-35814 Référence CVE CVE-2024-35819 https://www.cve.org/CVERecord?id=CVE-2024-35819 Référence CVE CVE-2024-35827 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-26813 Référence CVE CVE-2024-26814 https://www.cve.org/CVERecord?id=CVE-2024-26814 Référence CVE CVE-2024-26845 https://www.cve.org/CVERecord?id=CVE-2024-26845 Référence CVE CVE-2024-26889 https://www.cve.org/CVERecord?id=CVE-2024-26889 Référence CVE CVE-2024-26920 https://www.cve.org/CVERecord?id=CVE-2024-26920 Référence CVE CVE-2024-27414 https://www.cve.org/CVERecord?id=CVE-2024-27414 Référence CVE CVE-2024-27419 https://www.cve.org/CVERecord?id=CVE-2024-27419 Référence CVE CVE-2024-33619 https://www.cve.org/CVERecord?id=CVE-2024-33619 Référence CVE CVE-2024-34777 https://www.cve.org/CVERecord?id=CVE-2024-34777 Référence CVE CVE-2024-35247 https://www.cve.org/CVERecord?id=CVE-2024-35247 Référence CVE CVE-2024-35807 https://www.cve.org/CVERecord?id=CVE-2024-35807 Référence CVE CVE-2024-35827 https://www.cve.org/CVERecord?id=CVE-2024-35827 Référence CVE CVE-2024-35831 https://www.cve.org/CVERecord?id=CVE-2024-35831 Référence CVE CVE-2024-35843 https://www.cve.org/CVERecord?id=CVE-2024-35843 Référence CVE CVE-2024-35848 https://www.cve.org/CVERecord?id=CVE-2024-35848 Référence CVE CVE-2024-35857 https://www.cve.org/CVERecord?id=CVE-2024-35857 Référence CVE CVE-2024-35880 https://www.cve.org/CVERecord?id=CVE-2024-35880 Référence CVE CVE-2024-35884 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2023-52760 Référence CVE CVE-2024-25741 https://www.cve.org/CVERecord?id=CVE-2024-25741 Référence CVE CVE-2024-26629 https://www.cve.org/CVERecord?id=CVE-2024-26629 Référence CVE CVE-2024-27019 https://www.cve.org/CVERecord?id=CVE-2024-27019 Référence CVE CVE-2024-27397 https://www.cve.org/CVERecord?id=CVE-2024-27397 Référence CVE CVE-2024-31076 https://www.cve.org/CVERecord?id=CVE-2024-31076 Référence CVE CVE-2024-33621 https://www.cve.org/CVERecord?id=CVE-2024-33621 Référence CVE CVE-2024-33847 https://www.cve.org/CVERecord?id=CVE-2024-33847 Référence CVE CVE-2024-34027 https://www.cve.org/CVERecord?id=CVE-2024-34027 Référence CVE CVE-2024-35247 https://www.cve.org/CVERecord?id=CVE-2024-35247 Référence CVE CVE-2024-36014 https://www.cve.org/CVERecord?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-36016 https://www.cve.org/CVERecord?id=CVE-2024-36016 Référence CVE CVE-2024-36270 https://www.cve.org/CVERecord?id=CVE-2024-36270 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-36489 https://www.cve.org/CVERecord?id=CVE-2024-36489 Référence CVE CVE-2024-36894 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-26863 Référence CVE CVE-2024-26880 https://www.cve.org/CVERecord?id=CVE-2024-26880 Référence CVE CVE-2024-26894 https://www.cve.org/CVERecord?id=CVE-2024-26894 Référence CVE CVE-2024-26923 https://www.cve.org/CVERecord?id=CVE-2024-26923 Référence CVE CVE-2024-26928 https://www.cve.org/CVERecord?id=CVE-2024-26928 Référence CVE CVE-2024-26930 https://www.cve.org/CVERecord?id=CVE-2024-26930 Référence CVE CVE-2024-26973 https://www.cve.org/CVERecord?id=CVE-2024-26973 Référence CVE CVE-2024-27399 https://www.cve.org/CVERecord?id=CVE-2024-27399 Référence CVE CVE-2024-27410 https://www.cve.org/CVERecord?id=CVE-2024-27410 Référence CVE CVE-2024-35247 https://www.cve.org/CVERecord?id=CVE-2024-35247 Référence CVE CVE-2024-35789 https://www.cve.org/CVERecord?id=CVE-2024-35789 Référence CVE CVE-2024-35805 https://www.cve.org/CVERecord?id=CVE-2024-35805 Référence CVE CVE-2024-35807 https://www.cve.org/CVERecord?id=CVE-2024-35807 Référence CVE CVE-2024-35819 https://www.cve.org/CVERecord?id=CVE-2024-35819 Référence CVE CVE-2024-35822 https://www.cve.org/CVERecord?id=CVE-2024-35822 Référence CVE CVE-2024-35828 https://www.cve.org/CVERecord?id=CVE-2024-35828 Référence CVE CVE-2024-35835 https://www.cve.org/CVERecord?id=CVE-2024-35835 Référence CVE CVE-2024-35861 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-26921 Référence CVE CVE-2024-26923 https://www.cve.org/CVERecord?id=CVE-2024-26923 Référence CVE CVE-2024-26928 https://www.cve.org/CVERecord?id=CVE-2024-26928 Référence CVE CVE-2024-26930 https://www.cve.org/CVERecord?id=CVE-2024-26930 Référence CVE CVE-2024-26973 https://www.cve.org/CVERecord?id=CVE-2024-26973 Référence CVE CVE-2024-27399 https://www.cve.org/CVERecord?id=CVE-2024-27399 Référence CVE CVE-2024-27410 https://www.cve.org/CVERecord?id=CVE-2024-27410 Référence CVE CVE-2024-27432 https://www.cve.org/CVERecord?id=CVE-2024-27432 Référence CVE CVE-2024-33619 https://www.cve.org/CVERecord?id=CVE-2024-33619 Référence CVE CVE-2024-35247 https://www.cve.org/CVERecord?id=CVE-2024-35247 Référence CVE CVE-2024-35789 https://www.cve.org/CVERecord?id=CVE-2024-35789 Référence CVE CVE-2024-35790 https://www.cve.org/CVERecord?id=CVE-2024-35790 Référence CVE CVE-2024-35807 https://www.cve.org/CVERecord?id=CVE-2024-35807 Référence CVE CVE-2024-35814 https://www.cve.org/CVERecord?id=CVE-2024-35814 Référence CVE CVE-2024-35822 https://www.cve.org/CVERecord?id=CVE-2024-35822 Référence CVE CVE-2024-35835 https://www.cve.org/CVERecord?id=CVE-2024-35835 Référence CVE CVE-2024-35848 https://www.cve.org/CVERecord?id=CVE-2024-35848 Référence CVE CVE-2024-35857 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-018187Linux の 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: < 4.10, 5.10.219 ≤ 5.10.*, 5.15.161 ≤ 5.15.*, 6.1.93 ≤ 6.1.*, 6.6.33 ≤ 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 24 Jun 2024 · Last source change 11 May 2026, 20:10 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-35758
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-2024-35758↗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-2024-35247 · cve.blacktree.nl