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

In the Linux kernel through 5.16.10, certain binary files may have the exec-all attribute if they were built in approximately 2003 (e.g., with GCC 3.2.2 and Linux kernel 2.4.20)

Unknown · Unknown

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

High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 25 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.
  • A structured source references public exploit or proof-of-concept material.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 1.05% 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.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs Unknown Unknown 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 25 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 25 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 · sourcelinuxAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian 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-2022-29962

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 with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 25 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 through 5.16.10, certain binary files may have the exec-all attribute if they were built in approximately 2003 (e.g., with GCC 3.2.2 and Linux kernel 2.4.20). This can cause execution of bytes located in supposedly non-executable regions of a file.

What

In the Linux kernel through 5.16.10, certain binary files may have the exec-all attribute if they were built in approximately 2003 (e.g., with GCC 3.2.2 and Linux kernel 2.4.20). This can cause execution of bytes located in supposedly non-executable regions of a file.

Why

The product does not properly restrict reading from or writing to dynamically-managed code resources such as variables, objects, classes, attributes, functions, or executable instructions or statements.

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 through 5.16.10, certain binary files may have the exec-all attribute if they were built in approximately 2003 (e.g., with GCC 3.2.2 and Linux kernel 2.4.20). This can cause execution of bytes located in supposedly non-executable regions of a file.

Why

The product does not properly restrict reading from or writing to dynamically-managed code resources such as variables, objects, classes, attributes, functions, or executable instructions or statements.

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.
Reference recorded

A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.

Likely attack path
local access → Improper Control of Dynamically-Managed Code Resources → 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-913 ↗

CWE-913: Improper Control of Dynamically-Managed Code Resources. The product does not properly restrict reading from or writing to dynamically-managed code resources such as variables, objects, classes, attributes, functions, or executable instructions or statements.

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-913Public exploit reference
A

Official authority intelligence

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

BSI · German · WID-SEC-2024-0064Juniper Produkte: Mehrere Schwachstellen

Ein Angreifer aus dem angrenzenden Netzwerk oder ein entfernter, anonymer, authentisierter, lokaler oder physischer Angreifer kann mehrere Schwachstellen in Juniper JUNOS, Juniper JUNOS Evolved, Juniper SRX Series, Juniper EX Series, Juniper QFX Series, Juniper ACX Series, Juniper PTX Series und Juniper MX Series ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, vertrauliche Informationen offenzulegen, einen Denial-of-Service-Zustand herbeizuführen und seine Berechtigungen zu erweitern.

Official advisory ↗
BSI · German · WID-SEC-2022-0853Linux Kernel: Mehrere Schwachstellen

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen und beliebigen Code zur Ausführung zu bringen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20220223Security Bulletin 23 Feb 2022

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 23 Feb 2022, published on 23 February 2022. Open the linked bulletin for the product, severity and reference information published in that issue.

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

g/CVERecord?id=CVE-2021-47432 Référence CVE CVE-2021-47658 https://www.cve.org/CVERecord?id=CVE-2021-47658 Référence CVE CVE-2022-0400 https://www.cve.org/CVERecord?id=CVE-2022-0400 Référence CVE CVE-2022-0480 https://www.cve.org/CVERecord?id=CVE-2022-0480 Référence CVE CVE-2022-0987 https://www.cve.org/CVERecord?id=CVE-2022-0987 Référence CVE CVE-2022-1205 https://www.cve.org/CVERecord?id=CVE-2022-1205 Référence CVE CVE-2022-1247 https://www.cve.org/CVERecord?id=CVE-2022-1247 Référence CVE CVE-2022-23491 https://www.cve.org/CVERecord?id=CVE-2022-23491 Référence CVE CVE-2022-23825 https://www.cve.org/CVERecord?id=CVE-2022-23825 Référence CVE CVE-2022-25265 https://www.cve.org/CVERecord?id=CVE-2022-25265 Référence CVE CVE-2022-25836 https://www.cve.org/CVERecord?id=CVE-2022-25836 Référence CVE CVE-2022-25837 https://www.cve.org/CVERecord?id=CVE-2022-25837 Référence CVE CVE-2022-26047 https://www.cve.org/CVERecord?id=CVE-2022-26047 Référence CVE CVE-2022-27635 https://www.cve.org/CVERecord?id=CVE-2022-27635 Référence CVE CVE-2022-27943 https://www.cve.org/CVERecord?id=CVE-2022-27943 Référence CVE CVE-2022-2795 https://www.cve.org/CVERecord?id=CVE-2022-2795 Référence CVE CVE-2022-28667 https://www.cve.org/CVERecord?id=CVE-2022-28667 Référence CVE CVE-2022-28693 https://www.cve.org/CVERecord?id=CV

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

g/CVERecord?id=CVE-2021-47432 Référence CVE CVE-2021-47658 https://www.cve.org/CVERecord?id=CVE-2021-47658 Référence CVE CVE-2022-0400 https://www.cve.org/CVERecord?id=CVE-2022-0400 Référence CVE CVE-2022-0480 https://www.cve.org/CVERecord?id=CVE-2022-0480 Référence CVE CVE-2022-0987 https://www.cve.org/CVERecord?id=CVE-2022-0987 Référence CVE CVE-2022-1205 https://www.cve.org/CVERecord?id=CVE-2022-1205 Référence CVE CVE-2022-1247 https://www.cve.org/CVERecord?id=CVE-2022-1247 Référence CVE CVE-2022-23491 https://www.cve.org/CVERecord?id=CVE-2022-23491 Référence CVE CVE-2022-23825 https://www.cve.org/CVERecord?id=CVE-2022-23825 Référence CVE CVE-2022-25265 https://www.cve.org/CVERecord?id=CVE-2022-25265 Référence CVE CVE-2022-25836 https://www.cve.org/CVERecord?id=CVE-2022-25836 Référence CVE CVE-2022-25837 https://www.cve.org/CVERecord?id=CVE-2022-25837 Référence CVE CVE-2022-26047 https://www.cve.org/CVERecord?id=CVE-2022-26047 Référence CVE CVE-2022-27635 https://www.cve.org/CVERecord?id=CVE-2022-27635 Référence CVE CVE-2022-27943 https://www.cve.org/CVERecord?id=CVE-2022-27943 Référence CVE CVE-2022-2795 https://www.cve.org/CVERecord?id=CVE-2022-2795 Référence CVE CVE-2022-28667 https://www.cve.org/CVERecord?id=CVE-2022-28667 Référence CVE CVE-2022-28693 https://www.cve.org/CVERecord?id=CV

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

rg/CVERecord?id=CVE-2021-4204 Référence CVE CVE-2022-0168 https://www.cve.org/CVERecord?id=CVE-2022-0168 Référence CVE CVE-2022-0500 https://www.cve.org/CVERecord?id=CVE-2022-0500 Référence CVE CVE-2022-0617 https://www.cve.org/CVERecord?id=CVE-2022-0617 Référence CVE CVE-2022-1462 https://www.cve.org/CVERecord?id=CVE-2022-1462 Référence CVE CVE-2022-2078 https://www.cve.org/CVERecord?id=CVE-2022-2078 Référence CVE CVE-2022-21499 https://www.cve.org/CVERecord?id=CVE-2022-21499 Référence CVE CVE-2022-23222 https://www.cve.org/CVERecord?id=CVE-2022-23222 Référence CVE CVE-2022-24448 https://www.cve.org/CVERecord?id=CVE-2022-24448 Référence CVE CVE-2022-25265 https://www.cve.org/CVERecord?id=CVE-2022-25265 Référence CVE CVE-2022-2586 https://www.cve.org/CVERecord?id=CVE-2022-2586 Référence CVE CVE-2022-2663 https://www.cve.org/CVERecord?id=CVE-2022-2663 Référence CVE CVE-2022-28388 https://www.cve.org/CVERecord?id=CVE-2022-28388 Référence CVE CVE-2022-28390 https://www.cve.org/CVERecord?id=CVE-2022-28390 Référence CVE CVE-2022-28893 https://www.cve.org/CVERecord?id=CVE-2022-28893 Référence CVE CVE-2022-3524 https://www.cve.org/CVERecord?id=CVE-2022-3524 Référence CVE CVE-2022-3545 https://www.cve.org/CVERecord?id=CVE-2022-3545 Référence CVE CVE-2022-3566 https://www.cve.org/CVERecord?id=CVE-2022-

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0027Multiples vulnérabilités dans les produits Juniper Networks

cord?id=CVE-2022-1789 Référence CVE CVE-2022-20141 https://www.cve.org/CVERecord?id=CVE-2022-20141 Référence CVE CVE-2022-21699 https://www.cve.org/CVERecord?id=CVE-2022-21699 Référence CVE CVE-2022-2196 https://www.cve.org/CVERecord?id=CVE-2022-2196 Référence CVE CVE-2022-22164 https://www.cve.org/CVERecord?id=CVE-2022-22164 Référence CVE CVE-2022-22942 https://www.cve.org/CVERecord?id=CVE-2022-22942 Référence CVE CVE-2022-23302 https://www.cve.org/CVERecord?id=CVE-2022-23302 Référence CVE CVE-2022-23305 https://www.cve.org/CVERecord?id=CVE-2022-23305 Référence CVE CVE-2022-23307 https://www.cve.org/CVERecord?id=CVE-2022-23307 Référence CVE CVE-2022-25265 https://www.cve.org/CVERecord?id=CVE-2022-25265 Référence CVE CVE-2022-2663 https://www.cve.org/CVERecord?id=CVE-2022-2663 Référence CVE CVE-2022-2795 https://www.cve.org/CVERecord?id=CVE-2022-2795 Référence CVE CVE-2022-2873 https://www.cve.org/CVERecord?id=CVE-2022-2873 Référence CVE CVE-2022-2964 https://www.cve.org/CVERecord?id=CVE-2022-2964 Référence CVE CVE-2022-3028 https://www.cve.org/CVERecord?id=CVE-2022-3028 Référence CVE CVE-2022-30594 https://www.cve.org/CVERecord?id=CVE-2022-30594 Référence CVE CVE-2022-3239 https://www.cve.org/CVERecord?id=CVE-2022-3239 Référence CVE CVE-2022-3524 https://www.cve.org/CVERecord?id=CVE-2022-3524

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-0393Multiples vulnérabilités dans le noyau Linux de RedHat

g/CVERecord?id=CVE-2021-33655 Référence CVE CVE-2021-33656 https://www.cve.org/CVERecord?id=CVE-2021-33656 Référence CVE CVE-2022-1462 https://www.cve.org/CVERecord?id=CVE-2022-1462 Référence CVE CVE-2022-1679 https://www.cve.org/CVERecord?id=CVE-2022-1679 Référence CVE CVE-2022-1789 https://www.cve.org/CVERecord?id=CVE-2022-1789 Référence CVE CVE-2022-1882 https://www.cve.org/CVERecord?id=CVE-2022-1882 Référence CVE CVE-2022-20141 https://www.cve.org/CVERecord?id=CVE-2022-20141 Référence CVE CVE-2022-21505 https://www.cve.org/CVERecord?id=CVE-2022-21505 Référence CVE CVE-2022-2196 https://www.cve.org/CVERecord?id=CVE-2022-2196 Référence CVE CVE-2022-25265 https://www.cve.org/CVERecord?id=CVE-2022-25265 Référence CVE CVE-2022-2663 https://www.cve.org/CVERecord?id=CVE-2022-2663 Référence CVE CVE-2022-28388 https://www.cve.org/CVERecord?id=CVE-2022-28388 Référence CVE CVE-2022-3028 https://www.cve.org/CVERecord?id=CVE-2022-3028 Référence CVE CVE-2022-30594 https://www.cve.org/CVERecord?id=CVE-2022-30594 Référence CVE CVE-2022-3239 https://www.cve.org/CVERecord?id=CVE-2022-3239 Référence CVE CVE-2022-33743 https://www.cve.org/CVERecord?id=CVE-2022-33743 Référence CVE CVE-2022-3435 https://www.cve.org/CVERecord?id=CVE-2022-3435 Référence CVE CVE-2022-3522 https://www.cve.org/CVERecord?id=CVE-2022-

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2022-005900Linux Kernel における動的に操作されるコードリソースの不適切な制御に関する脆弱性

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
n/a
Fixed
An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
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 Feb 2022 · Last source change 3 Aug 2024, 04:36 UTC · CWE-913 · Improper Control of Dynamically-Managed Code Resources

CVE recordCVE.org · 5.1
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-2022-29962
Product sourceUnavailable
Remediation sourceCVE/CNA references
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

Missing structured fields: affected product. Missing data is not evidence of low risk; review the primary advisory.

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-29962↗Patch or update reference↗Public exploit 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-25265 · cve.blacktree.nl