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

ata: libata-transport: fix double ata_host_put() in ata_tport_add()

Linux · Linux

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

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

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

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

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.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: As exposure requiresRemediation target: Within 365 days

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

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 2 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.

6 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 2 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.0.10-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.0.10-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.0.10-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.0.10-1Debian Security Tracker ↗Source updated 6 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
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-12963

No EUVD known-exploited evidence

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

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

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 2 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: ata: libata-transport: fix double ata_host_put() in ata_tport_add() In the error path in ata_tport_add(), when calling put_device(), ata_tport_release() is called, it will put the refcount of 'ap->host'. And then ata_host_put() is called again, the refcount is decreased to 0, ata_host_release() is called, all ports are freed and set to null. When unbinding the device after failure, ata_host_stop() is called to release the resources, it leads a null-ptr-deref(), because all the ports all freed and null. Unable to handle kernel NULL pointer dereference at virtual address 0000000000000008 CPU: 7 PID: 18671 Comm: modprobe Kdump: loaded Tainted: G E 6.1.0-rc3+ #8 pstate: 80400009 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : ata_host_stop+0x3c/0x84 [libata] lr : release_nodes+0x64/0xd0 Call trace: ata_host_stop+0x3c/0x84 [libata] release_nodes+0x64/0xd0 devres_release_all+0xbc/0x1b0 device_unbind_cleanup+0x20/0x70 really_probe+0x158/0x320 __driver_probe_device+0x84/0x120 driver_probe_device+0x44/0x120 __driver_attach+0xb4/0x220 bus_for_each_dev+0x78/0xdc driver_attach+0x2c/0x40 bus_add_driver+0x184/0x240 driver_register+0x80/0x13c __pci_register_driver+0x4c/0x60 ahci_pci_driver_init+0x30/0x1000 [ahci] Fix this by removing redundant ata_host_put() in the error path.

What

In the Linux kernel, the following vulnerability has been resolved: ata: libata-transport: fix double ata_host_put() in ata_tport_add() In the error path in ata_tport_add(), when calling put_device(), ata_tport_release() is called, it will put the refcount of 'ap->host'. And then ata_host_put() is called again, the refcount is decreased to 0, ata_host_release() is called, all ports are freed and set to null. When unbinding the device after failure, ata_host_stop() is called to release the resources, it leads a null-ptr-deref(), because all the ports all freed and null. Unable to handle kernel NULL pointer dereference at virtual address 0000000000000008 CPU: 7 PID: 18671 Comm: modprobe Kdump: loaded Tainted: G E 6.1.0-rc3+ #8 pstate: 80400009 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : ata_host_stop+0x3c/0x84 [libata] lr : release_nodes+0x64/0xd0 Call trace: ata_host_stop+0x3c/0x84 [libata] release_nodes+0x64/0xd0 devres_release_all+0xbc/0x1b0 device_unbind_cleanup+0x20/0x70 really_probe+0x158/0x320 __driver_probe_device+0x84/0x120 driver_probe_device+0x44/0x120 __driver_attach+0xb4/0x220 bus_for_each_dev+0x78/0xdc driver_attach+0x2c/0x40 bus_add_driver+0x184/0x240 driver_register+0x80/0x13c __pci_register_driver+0x4c/0x60 ahci_pci_driver_init+0x30/0x1000 [ahci] Fix this by removing redundant ata_host_put() in the error path.

Why

The product calls free() twice on the same memory address.

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: ata: libata-transport: fix double ata_host_put() in ata_tport_add() In the error path in ata_tport_add(), when calling put_device(), ata_tport_release() is called, it will put the refcount of 'ap->host'. And then ata_host_put() is called again, the refcount is decreased to 0, ata_host_release() is called, all ports are freed and set to null. When unbinding the device after failure, ata_host_stop() is called to release the resources, it leads a null-ptr-deref(), because all the ports all freed and null. Unable to handle kernel NULL pointer dereference at virtual address 0000000000000008 CPU: 7 PID: 18671 Comm: modprobe Kdump: loaded Tainted: G E 6.1.0-rc3+ #8 pstate: 80400009 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : ata_host_stop+0x3c/0x84 [libata] lr : release_nodes+0x64/0xd0 Call trace: ata_host_stop+0x3c/0x84 [libata] release_nodes+0x64/0xd0 devres_release_all+0xbc/0x1b0 device_unbind_cleanup+0x20/0x70 really_probe+0x158/0x320 __driver_probe_device+0x84/0x120 driver_probe_device+0x44/0x120 __driver_attach+0xb4/0x220 bus_for_each_dev+0x78/0xdc driver_attach+0x2c/0x40 bus_add_driver+0x184/0x240 driver_register+0x80/0x13c __pci_register_driver+0x4c/0x60 ahci_pci_driver_init+0x30/0x1000 [ahci] Fix this by removing redundant ata_host_put() in the error path.

Why

The product calls free() twice on the same memory address.

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 → Double Free → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-415 ↗

CWE-415: Double Free. The product calls free() twice on the same memory address.

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

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

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

Official authority intelligence

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

Cyber Security Agency of Singapore · English · CSA-SB-20250507Security Bulletin 07 May 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 07 May 2025, published on 7 May 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

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

d?id=CVE-2022-49810 Référence CVE CVE-2022-49812 https://www.cve.org/CVERecord?id=CVE-2022-49812 Référence CVE CVE-2022-49813 https://www.cve.org/CVERecord?id=CVE-2022-49813 Référence CVE CVE-2022-49818 https://www.cve.org/CVERecord?id=CVE-2022-49818 Référence CVE CVE-2022-49821 https://www.cve.org/CVERecord?id=CVE-2022-49821 Référence CVE CVE-2022-49822 https://www.cve.org/CVERecord?id=CVE-2022-49822 Référence CVE CVE-2022-49823 https://www.cve.org/CVERecord?id=CVE-2022-49823 Référence CVE CVE-2022-49824 https://www.cve.org/CVERecord?id=CVE-2022-49824 Référence CVE CVE-2022-49825 https://www.cve.org/CVERecord?id=CVE-2022-49825 Référence CVE CVE-2022-49826 https://www.cve.org/CVERecord?id=CVE-2022-49826 Référence CVE CVE-2022-49827 https://www.cve.org/CVERecord?id=CVE-2022-49827 Référence CVE CVE-2022-49830 https://www.cve.org/CVERecord?id=CVE-2022-49830 Référence CVE CVE-2022-49832 https://www.cve.org/CVERecord?id=CVE-2022-49832 Référence CVE CVE-2022-49834 https://www.cve.org/CVERecord?id=CVE-2022-49834 Référence CVE CVE-2022-49835 https://www.cve.org/CVERecord?id=CVE-2022-49835 Référence CVE CVE-2022-49836 https://www.cve.org/CVERecord?id=CVE-2022-49836 Référence CVE CVE-2022-49839 https://www.cve.org/CVERecord?id=CVE-2022-49839 Référence CVE CVE-2022-49841 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2022-49810 Référence CVE CVE-2022-49812 https://www.cve.org/CVERecord?id=CVE-2022-49812 Référence CVE CVE-2022-49813 https://www.cve.org/CVERecord?id=CVE-2022-49813 Référence CVE CVE-2022-49818 https://www.cve.org/CVERecord?id=CVE-2022-49818 Référence CVE CVE-2022-49821 https://www.cve.org/CVERecord?id=CVE-2022-49821 Référence CVE CVE-2022-49822 https://www.cve.org/CVERecord?id=CVE-2022-49822 Référence CVE CVE-2022-49823 https://www.cve.org/CVERecord?id=CVE-2022-49823 Référence CVE CVE-2022-49824 https://www.cve.org/CVERecord?id=CVE-2022-49824 Référence CVE CVE-2022-49825 https://www.cve.org/CVERecord?id=CVE-2022-49825 Référence CVE CVE-2022-49826 https://www.cve.org/CVERecord?id=CVE-2022-49826 Référence CVE CVE-2022-49827 https://www.cve.org/CVERecord?id=CVE-2022-49827 Référence CVE CVE-2022-49830 https://www.cve.org/CVERecord?id=CVE-2022-49830 Référence CVE CVE-2022-49832 https://www.cve.org/CVERecord?id=CVE-2022-49832 Référence CVE CVE-2022-49834 https://www.cve.org/CVERecord?id=CVE-2022-49834 Référence CVE CVE-2022-49835 https://www.cve.org/CVERecord?id=CVE-2022-49835 Référence CVE CVE-2022-49836 https://www.cve.org/CVERecord?id=CVE-2022-49836 Référence CVE CVE-2022-49837 https://www.cve.org/CVERecord?id=CVE-2022-49837 Référence CVE CVE-2022-49839 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2022-49810 Référence CVE CVE-2022-49812 https://www.cve.org/CVERecord?id=CVE-2022-49812 Référence CVE CVE-2022-49813 https://www.cve.org/CVERecord?id=CVE-2022-49813 Référence CVE CVE-2022-49818 https://www.cve.org/CVERecord?id=CVE-2022-49818 Référence CVE CVE-2022-49821 https://www.cve.org/CVERecord?id=CVE-2022-49821 Référence CVE CVE-2022-49822 https://www.cve.org/CVERecord?id=CVE-2022-49822 Référence CVE CVE-2022-49823 https://www.cve.org/CVERecord?id=CVE-2022-49823 Référence CVE CVE-2022-49824 https://www.cve.org/CVERecord?id=CVE-2022-49824 Référence CVE CVE-2022-49825 https://www.cve.org/CVERecord?id=CVE-2022-49825 Référence CVE CVE-2022-49826 https://www.cve.org/CVERecord?id=CVE-2022-49826 Référence CVE CVE-2022-49827 https://www.cve.org/CVERecord?id=CVE-2022-49827 Référence CVE CVE-2022-49830 https://www.cve.org/CVERecord?id=CVE-2022-49830 Référence CVE CVE-2022-49832 https://www.cve.org/CVERecord?id=CVE-2022-49832 Référence CVE CVE-2022-49834 https://www.cve.org/CVERecord?id=CVE-2022-49834 Référence CVE CVE-2022-49835 https://www.cve.org/CVERecord?id=CVE-2022-49835 Référence CVE CVE-2022-49836 https://www.cve.org/CVERecord?id=CVE-2022-49836 Référence CVE CVE-2022-49839 https://www.cve.org/CVERecord?id=CVE-2022-49839 Référence CVE CVE-2022-49841 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2022-49810 Référence CVE CVE-2022-49812 https://www.cve.org/CVERecord?id=CVE-2022-49812 Référence CVE CVE-2022-49813 https://www.cve.org/CVERecord?id=CVE-2022-49813 Référence CVE CVE-2022-49818 https://www.cve.org/CVERecord?id=CVE-2022-49818 Référence CVE CVE-2022-49821 https://www.cve.org/CVERecord?id=CVE-2022-49821 Référence CVE CVE-2022-49822 https://www.cve.org/CVERecord?id=CVE-2022-49822 Référence CVE CVE-2022-49823 https://www.cve.org/CVERecord?id=CVE-2022-49823 Référence CVE CVE-2022-49824 https://www.cve.org/CVERecord?id=CVE-2022-49824 Référence CVE CVE-2022-49825 https://www.cve.org/CVERecord?id=CVE-2022-49825 Référence CVE CVE-2022-49826 https://www.cve.org/CVERecord?id=CVE-2022-49826 Référence CVE CVE-2022-49827 https://www.cve.org/CVERecord?id=CVE-2022-49827 Référence CVE CVE-2022-49830 https://www.cve.org/CVERecord?id=CVE-2022-49830 Référence CVE CVE-2022-49832 https://www.cve.org/CVERecord?id=CVE-2022-49832 Référence CVE CVE-2022-49834 https://www.cve.org/CVERecord?id=CVE-2022-49834 Référence CVE CVE-2022-49835 https://www.cve.org/CVERecord?id=CVE-2022-49835 Référence CVE CVE-2022-49836 https://www.cve.org/CVERecord?id=CVE-2022-49836 Référence CVE CVE-2022-49837 https://www.cve.org/CVERecord?id=CVE-2022-49837 Référence CVE CVE-2022-49839 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2022-49810 Référence CVE CVE-2022-49812 https://www.cve.org/CVERecord?id=CVE-2022-49812 Référence CVE CVE-2022-49813 https://www.cve.org/CVERecord?id=CVE-2022-49813 Référence CVE CVE-2022-49818 https://www.cve.org/CVERecord?id=CVE-2022-49818 Référence CVE CVE-2022-49821 https://www.cve.org/CVERecord?id=CVE-2022-49821 Référence CVE CVE-2022-49822 https://www.cve.org/CVERecord?id=CVE-2022-49822 Référence CVE CVE-2022-49823 https://www.cve.org/CVERecord?id=CVE-2022-49823 Référence CVE CVE-2022-49824 https://www.cve.org/CVERecord?id=CVE-2022-49824 Référence CVE CVE-2022-49825 https://www.cve.org/CVERecord?id=CVE-2022-49825 Référence CVE CVE-2022-49826 https://www.cve.org/CVERecord?id=CVE-2022-49826 Référence CVE CVE-2022-49827 https://www.cve.org/CVERecord?id=CVE-2022-49827 Référence CVE CVE-2022-49829 https://www.cve.org/CVERecord?id=CVE-2022-49829 Référence CVE CVE-2022-49830 https://www.cve.org/CVERecord?id=CVE-2022-49830 Référence CVE CVE-2022-49832 https://www.cve.org/CVERecord?id=CVE-2022-49832 Référence CVE CVE-2022-49834 https://www.cve.org/CVERecord?id=CVE-2022-49834 Référence CVE CVE-2022-49835 https://www.cve.org/CVERecord?id=CVE-2022-49835 Référence CVE CVE-2022-49836 https://www.cve.org/CVERecord?id=CVE-2022-49836 Référence CVE CVE-2022-49837 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2022-49810 Référence CVE CVE-2022-49812 https://www.cve.org/CVERecord?id=CVE-2022-49812 Référence CVE CVE-2022-49813 https://www.cve.org/CVERecord?id=CVE-2022-49813 Référence CVE CVE-2022-49818 https://www.cve.org/CVERecord?id=CVE-2022-49818 Référence CVE CVE-2022-49821 https://www.cve.org/CVERecord?id=CVE-2022-49821 Référence CVE CVE-2022-49822 https://www.cve.org/CVERecord?id=CVE-2022-49822 Référence CVE CVE-2022-49823 https://www.cve.org/CVERecord?id=CVE-2022-49823 Référence CVE CVE-2022-49824 https://www.cve.org/CVERecord?id=CVE-2022-49824 Référence CVE CVE-2022-49825 https://www.cve.org/CVERecord?id=CVE-2022-49825 Référence CVE CVE-2022-49826 https://www.cve.org/CVERecord?id=CVE-2022-49826 Référence CVE CVE-2022-49827 https://www.cve.org/CVERecord?id=CVE-2022-49827 Référence CVE CVE-2022-49830 https://www.cve.org/CVERecord?id=CVE-2022-49830 Référence CVE CVE-2022-49832 https://www.cve.org/CVERecord?id=CVE-2022-49832 Référence CVE CVE-2022-49834 https://www.cve.org/CVERecord?id=CVE-2022-49834 Référence CVE CVE-2022-49835 https://www.cve.org/CVERecord?id=CVE-2022-49835 Référence CVE CVE-2022-49836 https://www.cve.org/CVERecord?id=CVE-2022-49836 Référence CVE CVE-2022-49839 https://www.cve.org/CVERecord?id=CVE-2022-49839 Référence CVE CVE-2022-49841 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2022-026694Linux の Linux Kernel における二重解放に関する脆弱性

Linux の Linux Kernel には、二重解放に関する脆弱性が存在します。

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: 2623c7a5f2799569d8bb05eb211da524a8144cb3 < 30e12e2be27ac6c4be2af4163c70db381364706f, 2623c7a5f2799569d8bb05eb211da524a8144cb3 < bec9ded5404cb14e5f5470103d0973a2ff83d6a5, 2623c7a5f2799569d8bb05eb211da524a8144cb3 < ac471468f7c16cda2525909946ca13ddbcd14000, 2623c7a5f2799569d8bb05eb211da524a8144cb3 < 377ff82c33c0cb74562a353361b64b33c09562cf, 2623c7a5f2799569d8bb05eb211da524a8144cb3 < 865a6da40ba092c18292ae5f6194756131293745, 2623c7a5f2799569d8bb05eb211da524a8144cb3 < 8c76310740807ade5ecdab5888f70ecb6d35732e, 4.17
Fixed
Linux: < 4.17, 4.19.267 ≤ 4.19.*, 5.4.225 ≤ 5.4.*, 5.10.156 ≤ 5.10.*, 5.15.80 ≤ 5.15.*, 6.0.10 ≤ 6.0.*, 6.1 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 1 May 2025 · Last source change 5 Aug 2026, 08:56 UTC · CWE-415 · Double Free

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2025-12963
Product sourceCNA
Remediation sourceCVE/CNA references
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
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-2022-49826 · cve.blacktree.nl