BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2025-38510High confidence

kasan: remove kasan_find_vm_area() to prevent possible deadlock

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 21 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.15% 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 21 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.

25 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 21 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.41-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.147-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.16.3-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.16.3-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fdeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-intelAffected, 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
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-2025-25088

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 21 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: kasan: remove kasan_find_vm_area() to prevent possible deadlock find_vm_area() couldn't be called in atomic_context. If find_vm_area() is called to reports vm area information, kasan can trigger deadlock like: CPU0 CPU1 vmalloc(); alloc_vmap_area(); spin_lock(&vn->busy.lock) spin_lock_bh(&some_lock); <interrupt occurs> <in softirq> spin_lock(&some_lock); <access invalid address> kasan_report(); print_report(); print_address_description(); kasan_find_vm_area(); find_vm_area(); spin_lock(&vn->busy.lock) // deadlock! To prevent possible deadlock while kasan reports, remove kasan_find_vm_area().

What

In the Linux kernel, the following vulnerability has been resolved: kasan: remove kasan_find_vm_area() to prevent possible deadlock find_vm_area() couldn't be called in atomic_context. If find_vm_area() is called to reports vm area information, kasan can trigger deadlock like: CPU0 CPU1 vmalloc(); alloc_vmap_area(); spin_lock(&vn->busy.lock) spin_lock_bh(&some_lock); <interrupt occurs> <in softirq> spin_lock(&some_lock); <access invalid address> kasan_report(); print_report(); print_address_description(); kasan_find_vm_area(); find_vm_area(); spin_lock(&vn->busy.lock) // deadlock! To prevent possible deadlock while kasan reports, remove kasan_find_vm_area().

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: kasan: remove kasan_find_vm_area() to prevent possible deadlock find_vm_area() couldn't be called in atomic_context. If find_vm_area() is called to reports vm area information, kasan can trigger deadlock like: CPU0 CPU1 vmalloc(); alloc_vmap_area(); spin_lock(&vn->busy.lock) spin_lock_bh(&some_lock); <interrupt occurs> <in softirq> spin_lock(&some_lock); <access invalid address> kasan_report(); print_report(); print_address_description(); kasan_find_vm_area(); find_vm_area(); spin_lock(&vn->busy.lock) // deadlock! To prevent possible deadlock while kasan reports, remove kasan_find_vm_area().

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-2025-1858Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere nicht spezifizierte Angriffe durchzuführen.

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

d?id=CVE-2025-38321 Référence CVE CVE-2025-38322 https://www.cve.org/CVERecord?id=CVE-2025-38322 Référence CVE CVE-2025-38352 https://www.cve.org/CVERecord?id=CVE-2025-38352 Référence CVE CVE-2025-38359 https://www.cve.org/CVERecord?id=CVE-2025-38359 Référence CVE CVE-2025-38361 https://www.cve.org/CVERecord?id=CVE-2025-38361 Référence CVE CVE-2025-38379 https://www.cve.org/CVERecord?id=CVE-2025-38379 Référence CVE CVE-2025-38423 https://www.cve.org/CVERecord?id=CVE-2025-38423 Référence CVE CVE-2025-38505 https://www.cve.org/CVERecord?id=CVE-2025-38505 Référence CVE CVE-2025-38507 https://www.cve.org/CVERecord?id=CVE-2025-38507 Référence CVE CVE-2025-38510 https://www.cve.org/CVERecord?id=CVE-2025-38510 Référence CVE CVE-2025-38511 https://www.cve.org/CVERecord?id=CVE-2025-38511 Référence CVE CVE-2025-38512 https://www.cve.org/CVERecord?id=CVE-2025-38512 Référence CVE CVE-2025-38513 https://www.cve.org/CVERecord?id=CVE-2025-38513 Référence CVE CVE-2025-38515 https://www.cve.org/CVERecord?id=CVE-2025-38515 Référence CVE CVE-2025-38516 https://www.cve.org/CVERecord?id=CVE-2025-38516 Référence CVE CVE-2025-38520 https://www.cve.org/CVERecord?id=CVE-2025-38520 Référence CVE CVE-2025-38521 https://www.cve.org/CVERecord?id=CVE-2025-38521 Référence CVE CVE-2025-38529 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38494 Référence CVE CVE-2025-38495 https://www.cve.org/CVERecord?id=CVE-2025-38495 Référence CVE CVE-2025-38496 https://www.cve.org/CVERecord?id=CVE-2025-38496 Référence CVE CVE-2025-38497 https://www.cve.org/CVERecord?id=CVE-2025-38497 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38501 https://www.cve.org/CVERecord?id=CVE-2025-38501 Référence CVE CVE-2025-38503 https://www.cve.org/CVERecord?id=CVE-2025-38503 Référence CVE CVE-2025-38506 https://www.cve.org/CVERecord?id=CVE-2025-38506 Référence CVE CVE-2025-38507 https://www.cve.org/CVERecord?id=CVE-2025-38507 Référence CVE CVE-2025-38510 https://www.cve.org/CVERecord?id=CVE-2025-38510 Référence CVE CVE-2025-38511 https://www.cve.org/CVERecord?id=CVE-2025-38511 Référence CVE CVE-2025-38512 https://www.cve.org/CVERecord?id=CVE-2025-38512 Référence CVE CVE-2025-38513 https://www.cve.org/CVERecord?id=CVE-2025-38513 Référence CVE CVE-2025-38514 https://www.cve.org/CVERecord?id=CVE-2025-38514 Référence CVE CVE-2025-38515 https://www.cve.org/CVERecord?id=CVE-2025-38515 Référence CVE CVE-2025-38516 https://www.cve.org/CVERecord?id=CVE-2025-38516 Référence CVE CVE-2025-38520 https://www.cve.org/CVERecord?id=CVE-2025-38520 Référence CVE CVE-2025-38521 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38494 Référence CVE CVE-2025-38495 https://www.cve.org/CVERecord?id=CVE-2025-38495 Référence CVE CVE-2025-38496 https://www.cve.org/CVERecord?id=CVE-2025-38496 Référence CVE CVE-2025-38497 https://www.cve.org/CVERecord?id=CVE-2025-38497 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38501 https://www.cve.org/CVERecord?id=CVE-2025-38501 Référence CVE CVE-2025-38503 https://www.cve.org/CVERecord?id=CVE-2025-38503 Référence CVE CVE-2025-38506 https://www.cve.org/CVERecord?id=CVE-2025-38506 Référence CVE CVE-2025-38507 https://www.cve.org/CVERecord?id=CVE-2025-38507 Référence CVE CVE-2025-38510 https://www.cve.org/CVERecord?id=CVE-2025-38510 Référence CVE CVE-2025-38511 https://www.cve.org/CVERecord?id=CVE-2025-38511 Référence CVE CVE-2025-38512 https://www.cve.org/CVERecord?id=CVE-2025-38512 Référence CVE CVE-2025-38513 https://www.cve.org/CVERecord?id=CVE-2025-38513 Référence CVE CVE-2025-38514 https://www.cve.org/CVERecord?id=CVE-2025-38514 Référence CVE CVE-2025-38515 https://www.cve.org/CVERecord?id=CVE-2025-38515 Référence CVE CVE-2025-38516 https://www.cve.org/CVERecord?id=CVE-2025-38516 Référence CVE CVE-2025-38520 https://www.cve.org/CVERecord?id=CVE-2025-38520 Référence CVE CVE-2025-38521 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38494 Référence CVE CVE-2025-38495 https://www.cve.org/CVERecord?id=CVE-2025-38495 Référence CVE CVE-2025-38496 https://www.cve.org/CVERecord?id=CVE-2025-38496 Référence CVE CVE-2025-38497 https://www.cve.org/CVERecord?id=CVE-2025-38497 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38501 https://www.cve.org/CVERecord?id=CVE-2025-38501 Référence CVE CVE-2025-38503 https://www.cve.org/CVERecord?id=CVE-2025-38503 Référence CVE CVE-2025-38506 https://www.cve.org/CVERecord?id=CVE-2025-38506 Référence CVE CVE-2025-38507 https://www.cve.org/CVERecord?id=CVE-2025-38507 Référence CVE CVE-2025-38510 https://www.cve.org/CVERecord?id=CVE-2025-38510 Référence CVE CVE-2025-38511 https://www.cve.org/CVERecord?id=CVE-2025-38511 Référence CVE CVE-2025-38512 https://www.cve.org/CVERecord?id=CVE-2025-38512 Référence CVE CVE-2025-38513 https://www.cve.org/CVERecord?id=CVE-2025-38513 Référence CVE CVE-2025-38514 https://www.cve.org/CVERecord?id=CVE-2025-38514 Référence CVE CVE-2025-38515 https://www.cve.org/CVERecord?id=CVE-2025-38515 Référence CVE CVE-2025-38516 https://www.cve.org/CVERecord?id=CVE-2025-38516 Référence CVE CVE-2025-38520 https://www.cve.org/CVERecord?id=CVE-2025-38520 Référence CVE CVE-2025-38521 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38494 Référence CVE CVE-2025-38495 https://www.cve.org/CVERecord?id=CVE-2025-38495 Référence CVE CVE-2025-38496 https://www.cve.org/CVERecord?id=CVE-2025-38496 Référence CVE CVE-2025-38497 https://www.cve.org/CVERecord?id=CVE-2025-38497 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38501 https://www.cve.org/CVERecord?id=CVE-2025-38501 Référence CVE CVE-2025-38503 https://www.cve.org/CVERecord?id=CVE-2025-38503 Référence CVE CVE-2025-38506 https://www.cve.org/CVERecord?id=CVE-2025-38506 Référence CVE CVE-2025-38507 https://www.cve.org/CVERecord?id=CVE-2025-38507 Référence CVE CVE-2025-38510 https://www.cve.org/CVERecord?id=CVE-2025-38510 Référence CVE CVE-2025-38511 https://www.cve.org/CVERecord?id=CVE-2025-38511 Référence CVE CVE-2025-38512 https://www.cve.org/CVERecord?id=CVE-2025-38512 Référence CVE CVE-2025-38513 https://www.cve.org/CVERecord?id=CVE-2025-38513 Référence CVE CVE-2025-38514 https://www.cve.org/CVERecord?id=CVE-2025-38514 Référence CVE CVE-2025-38515 https://www.cve.org/CVERecord?id=CVE-2025-38515 Référence CVE CVE-2025-38516 https://www.cve.org/CVERecord?id=CVE-2025-38516 Référence CVE CVE-2025-38520 https://www.cve.org/CVERecord?id=CVE-2025-38520 Référence CVE CVE-2025-38521 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38494 Référence CVE CVE-2025-38495 https://www.cve.org/CVERecord?id=CVE-2025-38495 Référence CVE CVE-2025-38496 https://www.cve.org/CVERecord?id=CVE-2025-38496 Référence CVE CVE-2025-38497 https://www.cve.org/CVERecord?id=CVE-2025-38497 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38501 https://www.cve.org/CVERecord?id=CVE-2025-38501 Référence CVE CVE-2025-38503 https://www.cve.org/CVERecord?id=CVE-2025-38503 Référence CVE CVE-2025-38506 https://www.cve.org/CVERecord?id=CVE-2025-38506 Référence CVE CVE-2025-38507 https://www.cve.org/CVERecord?id=CVE-2025-38507 Référence CVE CVE-2025-38510 https://www.cve.org/CVERecord?id=CVE-2025-38510 Référence CVE CVE-2025-38511 https://www.cve.org/CVERecord?id=CVE-2025-38511 Référence CVE CVE-2025-38512 https://www.cve.org/CVERecord?id=CVE-2025-38512 Référence CVE CVE-2025-38513 https://www.cve.org/CVERecord?id=CVE-2025-38513 Référence CVE CVE-2025-38514 https://www.cve.org/CVERecord?id=CVE-2025-38514 Référence CVE CVE-2025-38515 https://www.cve.org/CVERecord?id=CVE-2025-38515 Référence CVE CVE-2025-38516 https://www.cve.org/CVERecord?id=CVE-2025-38516 Référence CVE CVE-2025-38520 https://www.cve.org/CVERecord?id=CVE-2025-38520 Référence CVE CVE-2025-38521 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38499 Référence CVE CVE-2025-38501 https://www.cve.org/CVERecord?id=CVE-2025-38501 Référence CVE CVE-2025-38502 https://www.cve.org/CVERecord?id=CVE-2025-38502 Référence CVE CVE-2025-38503 https://www.cve.org/CVERecord?id=CVE-2025-38503 Référence CVE CVE-2025-38505 https://www.cve.org/CVERecord?id=CVE-2025-38505 Référence CVE CVE-2025-38506 https://www.cve.org/CVERecord?id=CVE-2025-38506 Référence CVE CVE-2025-38507 https://www.cve.org/CVERecord?id=CVE-2025-38507 Référence CVE CVE-2025-38508 https://www.cve.org/CVERecord?id=CVE-2025-38508 Référence CVE CVE-2025-38509 https://www.cve.org/CVERecord?id=CVE-2025-38509 Référence CVE CVE-2025-38510 https://www.cve.org/CVERecord?id=CVE-2025-38510 Référence CVE CVE-2025-38511 https://www.cve.org/CVERecord?id=CVE-2025-38511 Référence CVE CVE-2025-38512 https://www.cve.org/CVERecord?id=CVE-2025-38512 Référence CVE CVE-2025-38513 https://www.cve.org/CVERecord?id=CVE-2025-38513 Référence CVE CVE-2025-38514 https://www.cve.org/CVERecord?id=CVE-2025-38514 Référence CVE CVE-2025-38515 https://www.cve.org/CVERecord?id=CVE-2025-38515 Référence CVE CVE-2025-38516 https://www.cve.org/CVERecord?id=CVE-2025-38516 Référence CVE CVE-2025-38517 https://www.cve.org/CVERecord?id=CVE-2025-38517 Référence CVE CVE-2025-38520 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38499 Référence CVE CVE-2025-38501 https://www.cve.org/CVERecord?id=CVE-2025-38501 Référence CVE CVE-2025-38502 https://www.cve.org/CVERecord?id=CVE-2025-38502 Référence CVE CVE-2025-38503 https://www.cve.org/CVERecord?id=CVE-2025-38503 Référence CVE CVE-2025-38505 https://www.cve.org/CVERecord?id=CVE-2025-38505 Référence CVE CVE-2025-38506 https://www.cve.org/CVERecord?id=CVE-2025-38506 Référence CVE CVE-2025-38507 https://www.cve.org/CVERecord?id=CVE-2025-38507 Référence CVE CVE-2025-38508 https://www.cve.org/CVERecord?id=CVE-2025-38508 Référence CVE CVE-2025-38509 https://www.cve.org/CVERecord?id=CVE-2025-38509 Référence CVE CVE-2025-38510 https://www.cve.org/CVERecord?id=CVE-2025-38510 Référence CVE CVE-2025-38511 https://www.cve.org/CVERecord?id=CVE-2025-38511 Référence CVE CVE-2025-38512 https://www.cve.org/CVERecord?id=CVE-2025-38512 Référence CVE CVE-2025-38513 https://www.cve.org/CVERecord?id=CVE-2025-38513 Référence CVE CVE-2025-38514 https://www.cve.org/CVERecord?id=CVE-2025-38514 Référence CVE CVE-2025-38515 https://www.cve.org/CVERecord?id=CVE-2025-38515 Référence CVE CVE-2025-38516 https://www.cve.org/CVERecord?id=CVE-2025-38516 Référence CVE CVE-2025-38517 https://www.cve.org/CVERecord?id=CVE-2025-38517 Référence CVE CVE-2025-38520 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38496 Référence CVE CVE-2025-38497 https://www.cve.org/CVERecord?id=CVE-2025-38497 Référence CVE CVE-2025-38501 https://www.cve.org/CVERecord?id=CVE-2025-38501 Référence CVE CVE-2025-38503 https://www.cve.org/CVERecord?id=CVE-2025-38503 Référence CVE CVE-2025-38505 https://www.cve.org/CVERecord?id=CVE-2025-38505 Référence CVE CVE-2025-38506 https://www.cve.org/CVERecord?id=CVE-2025-38506 Référence CVE CVE-2025-38507 https://www.cve.org/CVERecord?id=CVE-2025-38507 Référence CVE CVE-2025-38508 https://www.cve.org/CVERecord?id=CVE-2025-38508 Référence CVE CVE-2025-38509 https://www.cve.org/CVERecord?id=CVE-2025-38509 Référence CVE CVE-2025-38510 https://www.cve.org/CVERecord?id=CVE-2025-38510 Référence CVE CVE-2025-38511 https://www.cve.org/CVERecord?id=CVE-2025-38511 Référence CVE CVE-2025-38512 https://www.cve.org/CVERecord?id=CVE-2025-38512 Référence CVE CVE-2025-38513 https://www.cve.org/CVERecord?id=CVE-2025-38513 Référence CVE CVE-2025-38514 https://www.cve.org/CVERecord?id=CVE-2025-38514 Référence CVE CVE-2025-38515 https://www.cve.org/CVERecord?id=CVE-2025-38515 Référence CVE CVE-2025-38516 https://www.cve.org/CVERecord?id=CVE-2025-38516 Référence CVE CVE-2025-38517 https://www.cve.org/CVERecord?id=CVE-2025-38517 Référence CVE CVE-2025-38520 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38472 Référence CVE CVE-2025-38476 https://www.cve.org/CVERecord?id=CVE-2025-38476 Référence CVE CVE-2025-38488 https://www.cve.org/CVERecord?id=CVE-2025-38488 Référence CVE CVE-2025-38490 https://www.cve.org/CVERecord?id=CVE-2025-38490 Référence CVE CVE-2025-38491 https://www.cve.org/CVERecord?id=CVE-2025-38491 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38500 https://www.cve.org/CVERecord?id=CVE-2025-38500 Référence CVE CVE-2025-38503 https://www.cve.org/CVERecord?id=CVE-2025-38503 Référence CVE CVE-2025-38506 https://www.cve.org/CVERecord?id=CVE-2025-38506 Référence CVE CVE-2025-38510 https://www.cve.org/CVERecord?id=CVE-2025-38510 Référence CVE CVE-2025-38511 https://www.cve.org/CVERecord?id=CVE-2025-38511 Référence CVE CVE-2025-38512 https://www.cve.org/CVERecord?id=CVE-2025-38512 Référence CVE CVE-2025-38513 https://www.cve.org/CVERecord?id=CVE-2025-38513 Référence CVE CVE-2025-38514 https://www.cve.org/CVERecord?id=CVE-2025-38514 Référence CVE CVE-2025-38515 https://www.cve.org/CVERecord?id=CVE-2025-38515 Référence CVE CVE-2025-38516 https://www.cve.org/CVERecord?id=CVE-2025-38516 Référence CVE CVE-2025-38520 https://www.cve.org/CVERecord?id=CVE-2025-38520 Référence CVE CVE-2025-38521 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38466 Référence CVE CVE-2025-38472 https://www.cve.org/CVERecord?id=CVE-2025-38472 Référence CVE CVE-2025-38477 https://www.cve.org/CVERecord?id=CVE-2025-38477 Référence CVE CVE-2025-38488 https://www.cve.org/CVERecord?id=CVE-2025-38488 Référence CVE CVE-2025-38491 https://www.cve.org/CVERecord?id=CVE-2025-38491 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38500 https://www.cve.org/CVERecord?id=CVE-2025-38500 Référence CVE CVE-2025-38503 https://www.cve.org/CVERecord?id=CVE-2025-38503 Référence CVE CVE-2025-38506 https://www.cve.org/CVERecord?id=CVE-2025-38506 Référence CVE CVE-2025-38510 https://www.cve.org/CVERecord?id=CVE-2025-38510 Référence CVE CVE-2025-38512 https://www.cve.org/CVERecord?id=CVE-2025-38512 Référence CVE CVE-2025-38513 https://www.cve.org/CVERecord?id=CVE-2025-38513 Référence CVE CVE-2025-38514 https://www.cve.org/CVERecord?id=CVE-2025-38514 Référence CVE CVE-2025-38515 https://www.cve.org/CVERecord?id=CVE-2025-38515 Référence CVE CVE-2025-38516 https://www.cve.org/CVERecord?id=CVE-2025-38516 Référence CVE CVE-2025-38520 https://www.cve.org/CVERecord?id=CVE-2025-38520 Référence CVE CVE-2025-38524 https://www.cve.org/CVERecord?id=CVE-2025-38524 Référence CVE CVE-2025-38526 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38494 Référence CVE CVE-2025-38495 https://www.cve.org/CVERecord?id=CVE-2025-38495 Référence CVE CVE-2025-38497 https://www.cve.org/CVERecord?id=CVE-2025-38497 Référence CVE CVE-2025-38498 https://www.cve.org/CVERecord?id=CVE-2025-38498 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38500 https://www.cve.org/CVERecord?id=CVE-2025-38500 Référence CVE CVE-2025-38501 https://www.cve.org/CVERecord?id=CVE-2025-38501 Référence CVE CVE-2025-38502 https://www.cve.org/CVERecord?id=CVE-2025-38502 Référence CVE CVE-2025-38503 https://www.cve.org/CVERecord?id=CVE-2025-38503 Référence CVE CVE-2025-38510 https://www.cve.org/CVERecord?id=CVE-2025-38510 Référence CVE CVE-2025-38512 https://www.cve.org/CVERecord?id=CVE-2025-38512 Référence CVE CVE-2025-38513 https://www.cve.org/CVERecord?id=CVE-2025-38513 Référence CVE CVE-2025-38514 https://www.cve.org/CVERecord?id=CVE-2025-38514 Référence CVE CVE-2025-38515 https://www.cve.org/CVERecord?id=CVE-2025-38515 Référence CVE CVE-2025-38516 https://www.cve.org/CVERecord?id=CVE-2025-38516 Référence CVE CVE-2025-38520 https://www.cve.org/CVERecord?id=CVE-2025-38520 Référence CVE CVE-2025-38527 https://www.cve.org/CVERecord?id=CVE-2025-38527 Référence CVE CVE-2025-38528 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38472 Référence CVE CVE-2025-38477 https://www.cve.org/CVERecord?id=CVE-2025-38477 Référence CVE CVE-2025-38490 https://www.cve.org/CVERecord?id=CVE-2025-38490 Référence CVE CVE-2025-38491 https://www.cve.org/CVERecord?id=CVE-2025-38491 Référence CVE CVE-2025-38498 https://www.cve.org/CVERecord?id=CVE-2025-38498 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38500 https://www.cve.org/CVERecord?id=CVE-2025-38500 Référence CVE CVE-2025-38503 https://www.cve.org/CVERecord?id=CVE-2025-38503 Référence CVE CVE-2025-38506 https://www.cve.org/CVERecord?id=CVE-2025-38506 Référence CVE CVE-2025-38510 https://www.cve.org/CVERecord?id=CVE-2025-38510 Référence CVE CVE-2025-38511 https://www.cve.org/CVERecord?id=CVE-2025-38511 Référence CVE CVE-2025-38512 https://www.cve.org/CVERecord?id=CVE-2025-38512 Référence CVE CVE-2025-38513 https://www.cve.org/CVERecord?id=CVE-2025-38513 Référence CVE CVE-2025-38515 https://www.cve.org/CVERecord?id=CVE-2025-38515 Référence CVE CVE-2025-38516 https://www.cve.org/CVERecord?id=CVE-2025-38516 Référence CVE CVE-2025-38520 https://www.cve.org/CVERecord?id=CVE-2025-38520 Référence CVE CVE-2025-38521 https://www.cve.org/CVERecord?id=CVE-2025-38521 Référence CVE CVE-2025-38524 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38491 Référence CVE CVE-2025-38494 https://www.cve.org/CVERecord?id=CVE-2025-38494 Référence CVE CVE-2025-38495 https://www.cve.org/CVERecord?id=CVE-2025-38495 Référence CVE CVE-2025-38497 https://www.cve.org/CVERecord?id=CVE-2025-38497 Référence CVE CVE-2025-38498 https://www.cve.org/CVERecord?id=CVE-2025-38498 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38500 https://www.cve.org/CVERecord?id=CVE-2025-38500 Référence CVE CVE-2025-38503 https://www.cve.org/CVERecord?id=CVE-2025-38503 Référence CVE CVE-2025-38506 https://www.cve.org/CVERecord?id=CVE-2025-38506 Référence CVE CVE-2025-38510 https://www.cve.org/CVERecord?id=CVE-2025-38510 Référence CVE CVE-2025-38512 https://www.cve.org/CVERecord?id=CVE-2025-38512 Référence CVE CVE-2025-38513 https://www.cve.org/CVERecord?id=CVE-2025-38513 Référence CVE CVE-2025-38515 https://www.cve.org/CVERecord?id=CVE-2025-38515 Référence CVE CVE-2025-38516 https://www.cve.org/CVERecord?id=CVE-2025-38516 Référence CVE CVE-2025-38520 https://www.cve.org/CVERecord?id=CVE-2025-38520 Référence CVE CVE-2025-38524 https://www.cve.org/CVERecord?id=CVE-2025-38524 Référence CVE CVE-2025-38528 https://www.cve.org/CVERecord?id=CVE-2025-38528 Référence CVE CVE-2025-38529 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38473 Référence CVE CVE-2025-38474 https://www.cve.org/CVERecord?id=CVE-2025-38474 Référence CVE CVE-2025-38490 https://www.cve.org/CVERecord?id=CVE-2025-38490 Référence CVE CVE-2025-38491 https://www.cve.org/CVERecord?id=CVE-2025-38491 Référence CVE CVE-2025-38498 https://www.cve.org/CVERecord?id=CVE-2025-38498 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38500 https://www.cve.org/CVERecord?id=CVE-2025-38500 Référence CVE CVE-2025-38503 https://www.cve.org/CVERecord?id=CVE-2025-38503 Référence CVE CVE-2025-38506 https://www.cve.org/CVERecord?id=CVE-2025-38506 Référence CVE CVE-2025-38510 https://www.cve.org/CVERecord?id=CVE-2025-38510 Référence CVE CVE-2025-38512 https://www.cve.org/CVERecord?id=CVE-2025-38512 Référence CVE CVE-2025-38513 https://www.cve.org/CVERecord?id=CVE-2025-38513 Référence CVE CVE-2025-38515 https://www.cve.org/CVERecord?id=CVE-2025-38515 Référence CVE CVE-2025-38516 https://www.cve.org/CVERecord?id=CVE-2025-38516 Référence CVE CVE-2025-38520 https://www.cve.org/CVERecord?id=CVE-2025-38520 Référence CVE CVE-2025-38524 https://www.cve.org/CVERecord?id=CVE-2025-38524 Référence CVE CVE-2025-38528 https://www.cve.org/CVERecord?id=CVE-2025-38528 Référence CVE CVE-2025-38529 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38472 Référence CVE CVE-2025-38490 https://www.cve.org/CVERecord?id=CVE-2025-38490 Référence CVE CVE-2025-38491 https://www.cve.org/CVERecord?id=CVE-2025-38491 Référence CVE CVE-2025-38494 https://www.cve.org/CVERecord?id=CVE-2025-38494 Référence CVE CVE-2025-38495 https://www.cve.org/CVERecord?id=CVE-2025-38495 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38500 https://www.cve.org/CVERecord?id=CVE-2025-38500 Référence CVE CVE-2025-38503 https://www.cve.org/CVERecord?id=CVE-2025-38503 Référence CVE CVE-2025-38506 https://www.cve.org/CVERecord?id=CVE-2025-38506 Référence CVE CVE-2025-38510 https://www.cve.org/CVERecord?id=CVE-2025-38510 Référence CVE CVE-2025-38512 https://www.cve.org/CVERecord?id=CVE-2025-38512 Référence CVE CVE-2025-38513 https://www.cve.org/CVERecord?id=CVE-2025-38513 Référence CVE CVE-2025-38515 https://www.cve.org/CVERecord?id=CVE-2025-38515 Référence CVE CVE-2025-38516 https://www.cve.org/CVERecord?id=CVE-2025-38516 Référence CVE CVE-2025-38520 https://www.cve.org/CVERecord?id=CVE-2025-38520 Référence CVE CVE-2025-38524 https://www.cve.org/CVERecord?id=CVE-2025-38524 Référence CVE CVE-2025-38528 https://www.cve.org/CVERecord?id=CVE-2025-38528 Référence CVE CVE-2025-38529 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2025-024234Debian等の複数ベンダの製品におけるNULL ポインタデリファレンスに関する脆弱性

Linuxカーネルでは、find_vm_area()がatomicコンテキストで呼び出された場合、デッドロックが発生する可能性がありました。この問題を防ぐため、kasan_find_vm_area()は削除されました。

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
Linux: c056a364e9546bd513d1f5205f0ee316d8acb910 < 595f78d99b9051600233c0a5c4c47e1097e6ed01, c056a364e9546bd513d1f5205f0ee316d8acb910 < 8377d7744bdce5c4b3f1b58924eebd3fdc078dfc, c056a364e9546bd513d1f5205f0ee316d8acb910 < 2d89dab1ea6086e6cbe6fe92531b496fb6808cb9, c056a364e9546bd513d1f5205f0ee316d8acb910 < 0c3566d831def922cd56322c772a7b20d8b0e0c0, c056a364e9546bd513d1f5205f0ee316d8acb910 < 6ee9b3d84775944fb8c8a447961cd01274ac671c, 5.18
Fixed
Linux: < 5.18, 6.1.146 ≤ 6.1.*, 6.6.99 ≤ 6.6.*, 6.12.39 ≤ 6.12.*, 6.15.7 ≤ 6.15.*, 6.16 ≤ *
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 16 Aug 2025 · Last source change 11 May 2026, 21:29 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-2025-25088
Product sourceCNA
Remediation sourceCVE/CNA references
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
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-2025-38510 · cve.blacktree.nl