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

scsi: target: Fix WRITE_SAME No Data Buffer crash

Linux · Linux

7.5HighCVSS 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:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.45% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • 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: Within 30 daysRemediation target: Within 180 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.5.19.6-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.19.6-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.19.6-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.19.6-1Debian Security Tracker ↗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
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2022-21546 · CSAF 2.0 · revision 32 · interimSUSE Product Security TeamCVE-2022-21546
352 known affected

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

  • kernel-default as component of SLES-LTSS-TERADATA 15 SP2
  • kernel-source as component of SLES-LTSS-TERADATA 15 SP2
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
Summary
In the Linux kernel, the following vulnerability has been resolved: scsi: target: Fix WRITE_SAME No Data Buffer crash In newer version of the SBC specs, we have a NDOB bit that indicates there is no data buffer that gets written out. If this bit is set using commands like "sg_write_same --ndob" we will crash in target_core_iblock/file's execute_write_same handlers when we go to access the se_cmd->t_data_sg because its NULL. This patch adds a check for the NDOB bit in the common WRITE SAME code because we don't support it. And, it adds a check for zero SG elements in each handler in case the initiator tries to send a normal WRITE SAME with no data buffer.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2022-26770

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: scsi: target: Fix WRITE_SAME No Data Buffer crash In newer version of the SBC specs, we have a NDOB bit that indicates there is no data buffer that gets written out. If this bit is set using commands like "sg_write_same --ndob" we will crash in target_core_iblock/file's execute_write_same handlers when we go to access the se_cmd->t_data_sg because its NULL. This patch adds a check for the NDOB bit in the common WRITE SAME code because we don't support it. And, it adds a check for zero SG elements in each handler in case the initiator tries to send a normal WRITE SAME with no data buffer.

What

In the Linux kernel, the following vulnerability has been resolved: scsi: target: Fix WRITE_SAME No Data Buffer crash In newer version of the SBC specs, we have a NDOB bit that indicates there is no data buffer that gets written out. If this bit is set using commands like "sg_write_same --ndob" we will crash in target_core_iblock/file's execute_write_same handlers when we go to access the se_cmd->t_data_sg because its NULL. This patch adds a check for the NDOB bit in the common WRITE SAME code because we don't support it. And, it adds a check for zero SG elements in each handler in case the initiator tries to send a normal WRITE SAME with no data buffer.

Why

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

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.

What

In the Linux kernel, the following vulnerability has been resolved: scsi: target: Fix WRITE_SAME No Data Buffer crash In newer version of the SBC specs, we have a NDOB bit that indicates there is no data buffer that gets written out. If this bit is set using commands like "sg_write_same --ndob" we will crash in target_core_iblock/file's execute_write_same handlers when we go to access the se_cmd->t_data_sg because its NULL. This patch adds a check for the NDOB bit in the common WRITE SAME code because we don't support it. And, it adds a check for zero SG elements in each handler in case the initiator tries to send a normal WRITE SAME with no data buffer.

Why

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

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.

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
a network path → NULL Pointer Dereference → disrupt the affected service
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
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:N/AC:L/PR:N/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.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing 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
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedDenial of serviceCWE-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-0991Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff und weitere, nicht näher spezifizierte Angriffe durchzuführen.

Official advisory ↗
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-2025-AVI-0894Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2021-47037 Référence CVE CVE-2021-47070 https://www.cve.org/CVERecord?id=CVE-2021-47070 Référence CVE CVE-2021-47076 https://www.cve.org/CVERecord?id=CVE-2021-47076 Référence CVE CVE-2021-47183 https://www.cve.org/CVERecord?id=CVE-2021-47183 Référence CVE CVE-2021-47193 https://www.cve.org/CVERecord?id=CVE-2021-47193 Référence CVE CVE-2021-47412 https://www.cve.org/CVERecord?id=CVE-2021-47412 Référence CVE CVE-2021-47421 https://www.cve.org/CVERecord?id=CVE-2021-47421 Référence CVE CVE-2021-47455 https://www.cve.org/CVERecord?id=CVE-2021-47455 Référence CVE CVE-2021-47498 https://www.cve.org/CVERecord?id=CVE-2021-47498 Référence CVE CVE-2022-21546 https://www.cve.org/CVERecord?id=CVE-2022-21546 Référence CVE CVE-2022-49063 https://www.cve.org/CVERecord?id=CVE-2022-49063 Référence CVE CVE-2022-50327 https://www.cve.org/CVERecord?id=CVE-2022-50327 Référence CVE CVE-2023-52935 https://www.cve.org/CVERecord?id=CVE-2023-52935 Référence CVE CVE-2023-53259 https://www.cve.org/CVERecord?id=CVE-2023-53259 Référence CVE CVE-2024-26739 https://www.cve.org/CVERecord?id=CVE-2024-26739 Référence CVE CVE-2024-28956 https://www.cve.org/CVERecord?id=CVE-2024-28956 Référence CVE CVE-2024-35790 https://www.cve.org/CVERecord?id=CVE-2024-35790 Référence CVE CVE-2024-36331 https://www.cve.org/CVERecord?id=

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

rity/notices/USN-7727-2 Bulletin de sécurité Ubuntu USN-7712-2 du 02 septembre 2025 https://ubuntu.com/security/notices/USN-7712-2 Bulletin de sécurité Ubuntu USN-7725-3 du 02 septembre 2025 https://ubuntu.com/security/notices/USN-7725-3 Bulletin de sécurité Ubuntu USN-7726-4 du 02 septembre 2025 https://ubuntu.com/security/notices/USN-7726-4 Bulletin de sécurité Ubuntu USN-7727-3 du 02 septembre 2025 https://ubuntu.com/security/notices/USN-7727-3 Bulletin de sécurité Ubuntu USN-7737-1 du 03 septembre 2025 https://ubuntu.com/security/notices/USN-7737-1 Référence CVE CVE-2021-47345 https://www.cve.org/CVERecord?id=CVE-2021-47345 Référence CVE CVE-2022-21546 https://www.cve.org/CVERecord?id=CVE-2022-21546 Référence CVE CVE-2022-48893 https://www.cve.org/CVERecord?id=CVE-2022-48893 Référence CVE CVE-2022-49063 https://www.cve.org/CVERecord?id=CVE-2022-49063 Référence CVE CVE-2022-49168 https://www.cve.org/CVERecord?id=CVE-2022-49168 Référence CVE CVE-2022-49535 https://www.cve.org/CVERecord?id=CVE-2022-49535 Référence CVE CVE-2023-52477 https://www.cve.org/CVERecord?id=CVE-2023-52477 Référence CVE CVE-2024-26686 https://www.cve.org/CVERecord?id=CVE-2024-26686 Référence CVE CVE-2024-26739 https://www.cve.org/CVERecord?id=CVE-2024-26739 Référence CVE CVE-2024-27074 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2022-21527 Référence CVE CVE-2022-21528 https://www.cve.org/CVERecord?id=CVE-2022-21528 Référence CVE CVE-2022-21529 https://www.cve.org/CVERecord?id=CVE-2022-21529 Référence CVE CVE-2022-21530 https://www.cve.org/CVERecord?id=CVE-2022-21530 Référence CVE CVE-2022-21531 https://www.cve.org/CVERecord?id=CVE-2022-21531 Référence CVE CVE-2022-21534 https://www.cve.org/CVERecord?id=CVE-2022-21534 Référence CVE CVE-2022-21537 https://www.cve.org/CVERecord?id=CVE-2022-21537 Référence CVE CVE-2022-21538 https://www.cve.org/CVERecord?id=CVE-2022-21538 Référence CVE CVE-2022-21539 https://www.cve.org/CVERecord?id=CVE-2022-21539 Référence CVE CVE-2022-21546 https://www.cve.org/CVERecord?id=CVE-2022-21546 Référence CVE CVE-2022-21547 https://www.cve.org/CVERecord?id=CVE-2022-21547 Référence CVE CVE-2022-21553 https://www.cve.org/CVERecord?id=CVE-2022-21553 Référence CVE CVE-2022-21556 https://www.cve.org/CVERecord?id=CVE-2022-21556 Référence CVE CVE-2022-21569 https://www.cve.org/CVERecord?id=CVE-2022-21569 Référence CVE CVE-2022-21589 https://www.cve.org/CVERecord?id=CVE-2022-21589 Référence CVE CVE-2022-21592 https://www.cve.org/CVERecord?id=CVE-2022-21592 Référence CVE CVE-2022-21595 https://www.cve.org/CVERecord?id=CVE-2022-21595 Référence CVE CVE-2022-21608 https://www.cve.org/CVERecord?id=

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

d'Ubuntu. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire, une atteinte à la confidentialité des données et une atteinte à l'intégrité des données. Solutions Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation). Documentation Bulletin de sécurité Ubuntu USN-7711-1 du 22 août 2025 https://ubuntu.com/security/notices/USN-7711-1 Bulletin de sécurité Ubuntu USN-7712-1 du 22 août 2025 https://ubuntu.com/security/notices/USN-7712-1 Bulletin de sécurité Ubuntu USN-7719-1 du 26 août 2025 https://ubuntu.com/security/notices/USN-7719-1 Référence CVE CVE-2022-21546 https://www.cve.org/CVERecord?id=CVE-2022-21546 Référence CVE CVE-2022-48893 https://www.cve.org/CVERecord?id=CVE-2022-48893 Référence CVE CVE-2022-49063 https://www.cve.org/CVERecord?id=CVE-2022-49063 Référence CVE CVE-2022-49168 https://www.cve.org/CVERecord?id=CVE-2022-49168 Référence CVE CVE-2022-49535 https://www.cve.org/CVERecord?id=CVE-2022-49535 Référence CVE CVE-2024-26686 https://www.cve.org/CVERecord?id=CVE-2024-26686 Référence CVE CVE-2024-26739 https://www.cve.org/CVERecord?id=CVE-2024-26739 Référence CVE CVE-2024-27402 https://www.cve.org/CVERecord?id=CVE-2024-27402 Référence CVE CVE-2024-35790 https://www.cve.org/CVERecord?id=

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

rity/notices/USN-7682-4 Bulletin de sécurité Ubuntu USN-7671-3 du 04 août 2025 https://ubuntu.com/security/notices/USN-7671-3 Bulletin de sécurité Ubuntu USN-7685-1 du 05 août 2025 https://ubuntu.com/security/notices/USN-7685-1 Bulletin de sécurité Ubuntu USN-7685-2 du 05 août 2025 https://ubuntu.com/security/notices/USN-7685-2 Bulletin de sécurité Ubuntu USN-7685-3 du 05 août 2025 https://ubuntu.com/security/notices/USN-7685-3 Bulletin de sécurité Ubuntu USN-7685-4 du 05 août 2025 https://ubuntu.com/security/notices/USN-7685-4 Bulletin de sécurité Ubuntu USN-7686-1 du 05 août 2025 https://ubuntu.com/security/notices/USN-7686-1 Référence CVE CVE-2022-21546 https://www.cve.org/CVERecord?id=CVE-2022-21546 Référence CVE CVE-2022-48893 https://www.cve.org/CVERecord?id=CVE-2022-48893 Référence CVE CVE-2022-49063 https://www.cve.org/CVERecord?id=CVE-2022-49063 Référence CVE CVE-2022-49168 https://www.cve.org/CVERecord?id=CVE-2022-49168 Référence CVE CVE-2022-49535 https://www.cve.org/CVERecord?id=CVE-2022-49535 Référence CVE CVE-2023-52572 https://www.cve.org/CVERecord?id=CVE-2023-52572 Référence CVE CVE-2023-52757 https://www.cve.org/CVERecord?id=CVE-2023-52757 Référence CVE CVE-2023-52885 https://www.cve.org/CVERecord?id=CVE-2023-52885 Référence CVE CVE-2023-52975 https://www.cve.org/CVERecord?id=

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

ation Bulletin de sécurité Ubuntu USN-7671-1 du 25 juillet 2025 https://ubuntu.com/security/notices/USN-7671-1 Bulletin de sécurité Ubuntu USN-7654-5 du 29 juillet 2025 https://ubuntu.com/security/notices/USN-7654-5 Bulletin de sécurité Ubuntu USN-7671-2 du 29 juillet 2025 https://ubuntu.com/security/notices/USN-7671-2 Bulletin de sécurité Ubuntu USN-7608-7 du 30 juillet 2025 https://ubuntu.com/security/notices/USN-7608-7 Bulletin de sécurité Ubuntu USN-7681-1 du 30 juillet 2025 https://ubuntu.com/security/notices/USN-7681-1 Bulletin de sécurité Ubuntu USN-7682-1 du 30 juillet 2025 https://ubuntu.com/security/notices/USN-7682-1 Référence CVE CVE-2022-21546 https://www.cve.org/CVERecord?id=CVE-2022-21546 Référence CVE CVE-2022-48893 https://www.cve.org/CVERecord?id=CVE-2022-48893 Référence CVE CVE-2022-49063 https://www.cve.org/CVERecord?id=CVE-2022-49063 Référence CVE CVE-2022-49168 https://www.cve.org/CVERecord?id=CVE-2022-49168 Référence CVE CVE-2022-49535 https://www.cve.org/CVERecord?id=CVE-2022-49535 Référence CVE CVE-2023-52572 https://www.cve.org/CVERecord?id=CVE-2023-52572 Référence CVE CVE-2023-52757 https://www.cve.org/CVERecord?id=CVE-2023-52757 Référence CVE CVE-2024-26686 https://www.cve.org/CVERecord?id=CVE-2024-26686 Référence CVE CVE-2024-26739 https://www.cve.org/CVERecord?id=

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

651-3 Bulletin de sécurité Ubuntu USN-7651-4 du 22 juillet 2025 https://ubuntu.com/security/notices/USN-7651-4 Bulletin de sécurité Ubuntu USN-7654-4 du 22 juillet 2025 https://ubuntu.com/security/notices/USN-7654-4 Bulletin de sécurité Ubuntu USN-7665-1 du 22 juillet 2025 https://ubuntu.com/security/notices/USN-7665-1 Bulletin de sécurité Ubuntu USN-7651-5 du 24 juillet 2025 https://ubuntu.com/security/notices/USN-7651-5 Bulletin de sécurité Ubuntu USN-7651-6 du 24 juillet 2025 https://ubuntu.com/security/notices/USN-7651-6 Bulletin de sécurité Ubuntu USN-7665-2 du 24 juillet 2025 https://ubuntu.com/security/notices/USN-7665-2 Référence CVE CVE-2022-21546 https://www.cve.org/CVERecord?id=CVE-2022-21546 Référence CVE CVE-2022-48893 https://www.cve.org/CVERecord?id=CVE-2022-48893 Référence CVE CVE-2022-49063 https://www.cve.org/CVERecord?id=CVE-2022-49063 Référence CVE CVE-2022-49168 https://www.cve.org/CVERecord?id=CVE-2022-49168 Référence CVE CVE-2022-49535 https://www.cve.org/CVERecord?id=CVE-2022-49535 Référence CVE CVE-2022-49636 https://www.cve.org/CVERecord?id=CVE-2022-49636 Référence CVE CVE-2022-49728 https://www.cve.org/CVERecord?id=CVE-2022-49728 Référence CVE CVE-2023-52572 https://www.cve.org/CVERecord?id=CVE-2023-52572 Référence CVE CVE-2023-52757 https://www.cve.org/CVERecord?id=

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

nouncement/2025/suse-su-202502334-1 Bulletin de sécurité SUSE SUSE-SU-2025:02335-1 du 16 juillet 2025 https://www.suse.com/support/update/announcement/2025/suse-su-202502335-1 Référence CVE CVE-2021-47212 https://www.cve.org/CVERecord?id=CVE-2021-47212 Référence CVE CVE-2021-47455 https://www.cve.org/CVERecord?id=CVE-2021-47455 Référence CVE CVE-2021-47527 https://www.cve.org/CVERecord?id=CVE-2021-47527 Référence CVE CVE-2021-47557 https://www.cve.org/CVERecord?id=CVE-2021-47557 Référence CVE CVE-2021-47595 https://www.cve.org/CVERecord?id=CVE-2021-47595 Référence CVE CVE-2022-1679 https://www.cve.org/CVERecord?id=CVE-2022-1679 Référence CVE CVE-2022-21546 https://www.cve.org/CVERecord?id=CVE-2022-21546 Référence CVE CVE-2022-2585 https://www.cve.org/CVERecord?id=CVE-2022-2585 Référence CVE CVE-2022-2586 https://www.cve.org/CVERecord?id=CVE-2022-2586 Référence CVE CVE-2022-2905 https://www.cve.org/CVERecord?id=CVE-2022-2905 Référence CVE CVE-2022-3903 https://www.cve.org/CVERecord?id=CVE-2022-3903 Référence CVE CVE-2022-4095 https://www.cve.org/CVERecord?id=CVE-2022-4095 Référence CVE CVE-2022-4662 https://www.cve.org/CVERecord?id=CVE-2022-4662 Référence CVE CVE-2022-49154 https://www.cve.org/CVERecord?id=CVE-2022-49154 Référence CVE CVE-2022-49622 https://www.cve.org/CVERecord?id=CVE-2022-496

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2022-026715Linux の 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: < 3.8, 5.4.294 ≤ 5.4.*, 5.10.238 ≤ 5.10.*, 5.15.182 ≤ 5.15.*, 5.19 ≤ *
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. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 2 May 2025 · Last source change 5 Aug 2026, 08:51 UTC · CWE-476 · NULL Pointer Dereference

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-2022-26770
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceCISA ADP
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2022-26770↗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-2022-21546 · cve.blacktree.nl