BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-31660High confidence

nfc: pn533: allocate rx skb before consuming bytes

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 20 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.16% 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 20 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.

24 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 20 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.85-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.170-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.19.13-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.19.13-1Debian Security Tracker ↗Source updated 6 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-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
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-2026-31660 · CSAF 2.0 · revision 8 · interimSUSE Product Security TeamCVE-2026-31660
168 known affected

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

  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4
Summary
In the Linux kernel, the following vulnerability has been resolved: nfc: pn533: allocate rx skb before consuming bytes pn532_receive_buf() reports the number of accepted bytes to the serdev core. The current code consumes bytes into recv_skb and may already hand a complete frame to pn533_recv_frame() before allocating a fresh receive buffer. If that alloc_skb() fails, the callback returns 0 even though it has already consumed bytes, and it leaves recv_skb as NULL for the next receive callback. That breaks the receive_buf() accounting contract and can also lead to a NULL dereference on the next skb_put_u8(). Allocate the receive skb lazily before consuming the next byte instead. If allocation fails, return the number of bytes already accepted.
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-2026-25553

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 20 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: nfc: pn533: allocate rx skb before consuming bytes pn532_receive_buf() reports the number of accepted bytes to the serdev core. The current code consumes bytes into recv_skb and may already hand a complete frame to pn533_recv_frame() before allocating a fresh receive buffer. If that alloc_skb() fails, the callback returns 0 even though it has already consumed bytes, and it leaves recv_skb as NULL for the next receive callback. That breaks the receive_buf() accounting contract and can also lead to a NULL dereference on the next skb_put_u8(). Allocate the receive skb lazily before consuming the next byte instead. If allocation fails, return the number of bytes already accepted.

What

In the Linux kernel, the following vulnerability has been resolved: nfc: pn533: allocate rx skb before consuming bytes pn532_receive_buf() reports the number of accepted bytes to the serdev core. The current code consumes bytes into recv_skb and may already hand a complete frame to pn533_recv_frame() before allocating a fresh receive buffer. If that alloc_skb() fails, the callback returns 0 even though it has already consumed bytes, and it leaves recv_skb as NULL for the next receive callback. That breaks the receive_buf() accounting contract and can also lead to a NULL dereference on the next skb_put_u8(). Allocate the receive skb lazily before consuming the next byte instead. If allocation fails, return the number of bytes already accepted.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

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: nfc: pn533: allocate rx skb before consuming bytes pn532_receive_buf() reports the number of accepted bytes to the serdev core. The current code consumes bytes into recv_skb and may already hand a complete frame to pn533_recv_frame() before allocating a fresh receive buffer. If that alloc_skb() fails, the callback returns 0 even though it has already consumed bytes, and it leaves recv_skb as NULL for the next receive callback. That breaks the receive_buf() accounting contract and can also lead to a NULL dereference on the next skb_put_u8(). Allocate the receive skb lazily before consuming the next byte instead. If allocation fails, return the number of bytes already accepted.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

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 → vulnerable operation → 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.
CWE not yet assigned
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.
A

Official authority intelligence

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

BSI · German · WID-SEC-2026-1279Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, welche zu einem Denial-of-Service-Zustand, einer Rechteausweitung, der Ausführung von Code oder einer Speicherbeschädigung führen könnten.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260429Security Bulletin 29 Apr 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 29 Apr 2026, published on 29 April 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

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

d?id=CVE-2026-31627 Référence CVE CVE-2026-31628 https://www.cve.org/CVERecord?id=CVE-2026-31628 Référence CVE CVE-2026-31629 https://www.cve.org/CVERecord?id=CVE-2026-31629 Référence CVE CVE-2026-31630 https://www.cve.org/CVERecord?id=CVE-2026-31630 Référence CVE CVE-2026-31634 https://www.cve.org/CVERecord?id=CVE-2026-31634 Référence CVE CVE-2026-31642 https://www.cve.org/CVERecord?id=CVE-2026-31642 Référence CVE CVE-2026-31651 https://www.cve.org/CVERecord?id=CVE-2026-31651 Référence CVE CVE-2026-31656 https://www.cve.org/CVERecord?id=CVE-2026-31656 Référence CVE CVE-2026-31658 https://www.cve.org/CVERecord?id=CVE-2026-31658 Référence CVE CVE-2026-31660 https://www.cve.org/CVERecord?id=CVE-2026-31660 Référence CVE CVE-2026-31661 https://www.cve.org/CVERecord?id=CVE-2026-31661 Référence CVE CVE-2026-31662 https://www.cve.org/CVERecord?id=CVE-2026-31662 Référence CVE CVE-2026-31664 https://www.cve.org/CVERecord?id=CVE-2026-31664 Référence CVE CVE-2026-31665 https://www.cve.org/CVERecord?id=CVE-2026-31665 Référence CVE CVE-2026-31667 https://www.cve.org/CVERecord?id=CVE-2026-31667 Référence CVE CVE-2026-31670 https://www.cve.org/CVERecord?id=CVE-2026-31670 Référence CVE CVE-2026-31671 https://www.cve.org/CVERecord?id=CVE-2026-31671 Référence CVE CVE-2026-31672 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31636 Référence CVE CVE-2026-31637 https://www.cve.org/CVERecord?id=CVE-2026-31637 Référence CVE CVE-2026-31642 https://www.cve.org/CVERecord?id=CVE-2026-31642 Référence CVE CVE-2026-31649 https://www.cve.org/CVERecord?id=CVE-2026-31649 Référence CVE CVE-2026-31651 https://www.cve.org/CVERecord?id=CVE-2026-31651 Référence CVE CVE-2026-31656 https://www.cve.org/CVERecord?id=CVE-2026-31656 Référence CVE CVE-2026-31657 https://www.cve.org/CVERecord?id=CVE-2026-31657 Référence CVE CVE-2026-31658 https://www.cve.org/CVERecord?id=CVE-2026-31658 Référence CVE CVE-2026-31659 https://www.cve.org/CVERecord?id=CVE-2026-31659 Référence CVE CVE-2026-31660 https://www.cve.org/CVERecord?id=CVE-2026-31660 Référence CVE CVE-2026-31661 https://www.cve.org/CVERecord?id=CVE-2026-31661 Référence CVE CVE-2026-31662 https://www.cve.org/CVERecord?id=CVE-2026-31662 Référence CVE CVE-2026-31664 https://www.cve.org/CVERecord?id=CVE-2026-31664 Référence CVE CVE-2026-31665 https://www.cve.org/CVERecord?id=CVE-2026-31665 Référence CVE CVE-2026-31667 https://www.cve.org/CVERecord?id=CVE-2026-31667 Référence CVE CVE-2026-31668 https://www.cve.org/CVERecord?id=CVE-2026-31668 Référence CVE CVE-2026-31670 https://www.cve.org/CVERecord?id=CVE-2026-31670 Référence CVE CVE-2026-31671 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31645 Référence CVE CVE-2026-31646 https://www.cve.org/CVERecord?id=CVE-2026-31646 Référence CVE CVE-2026-31648 https://www.cve.org/CVERecord?id=CVE-2026-31648 Référence CVE CVE-2026-31649 https://www.cve.org/CVERecord?id=CVE-2026-31649 Référence CVE CVE-2026-31651 https://www.cve.org/CVERecord?id=CVE-2026-31651 Référence CVE CVE-2026-31655 https://www.cve.org/CVERecord?id=CVE-2026-31655 Référence CVE CVE-2026-31656 https://www.cve.org/CVERecord?id=CVE-2026-31656 Référence CVE CVE-2026-31657 https://www.cve.org/CVERecord?id=CVE-2026-31657 Référence CVE CVE-2026-31658 https://www.cve.org/CVERecord?id=CVE-2026-31658 Référence CVE CVE-2026-31660 https://www.cve.org/CVERecord?id=CVE-2026-31660 Référence CVE CVE-2026-31661 https://www.cve.org/CVERecord?id=CVE-2026-31661 Référence CVE CVE-2026-31662 https://www.cve.org/CVERecord?id=CVE-2026-31662 Référence CVE CVE-2026-31664 https://www.cve.org/CVERecord?id=CVE-2026-31664 Référence CVE CVE-2026-31665 https://www.cve.org/CVERecord?id=CVE-2026-31665 Référence CVE CVE-2026-31667 https://www.cve.org/CVERecord?id=CVE-2026-31667 Référence CVE CVE-2026-31668 https://www.cve.org/CVERecord?id=CVE-2026-31668 Référence CVE CVE-2026-31670 https://www.cve.org/CVERecord?id=CVE-2026-31670 Référence CVE CVE-2026-31671 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31625 Référence CVE CVE-2026-31626 https://www.cve.org/CVERecord?id=CVE-2026-31626 Référence CVE CVE-2026-31627 https://www.cve.org/CVERecord?id=CVE-2026-31627 Référence CVE CVE-2026-31628 https://www.cve.org/CVERecord?id=CVE-2026-31628 Référence CVE CVE-2026-31629 https://www.cve.org/CVERecord?id=CVE-2026-31629 Référence CVE CVE-2026-31651 https://www.cve.org/CVERecord?id=CVE-2026-31651 Référence CVE CVE-2026-31656 https://www.cve.org/CVERecord?id=CVE-2026-31656 Référence CVE CVE-2026-31657 https://www.cve.org/CVERecord?id=CVE-2026-31657 Référence CVE CVE-2026-31659 https://www.cve.org/CVERecord?id=CVE-2026-31659 Référence CVE CVE-2026-31660 https://www.cve.org/CVERecord?id=CVE-2026-31660 Référence CVE CVE-2026-31661 https://www.cve.org/CVERecord?id=CVE-2026-31661 Référence CVE CVE-2026-31667 https://www.cve.org/CVERecord?id=CVE-2026-31667 Référence CVE CVE-2026-31672 https://www.cve.org/CVERecord?id=CVE-2026-31672 Référence CVE CVE-2026-31677 https://www.cve.org/CVERecord?id=CVE-2026-31677 Référence CVE CVE-2026-31687 https://www.cve.org/CVERecord?id=CVE-2026-31687 Référence CVE CVE-2026-31697 https://www.cve.org/CVERecord?id=CVE-2026-31697 Référence CVE CVE-2026-31698 https://www.cve.org/CVERecord?id=CVE-2026-31698 Référence CVE CVE-2026-31699 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31627 Référence CVE CVE-2026-31628 https://www.cve.org/CVERecord?id=CVE-2026-31628 Référence CVE CVE-2026-31629 https://www.cve.org/CVERecord?id=CVE-2026-31629 Référence CVE CVE-2026-31630 https://www.cve.org/CVERecord?id=CVE-2026-31630 Référence CVE CVE-2026-31634 https://www.cve.org/CVERecord?id=CVE-2026-31634 Référence CVE CVE-2026-31642 https://www.cve.org/CVERecord?id=CVE-2026-31642 Référence CVE CVE-2026-31651 https://www.cve.org/CVERecord?id=CVE-2026-31651 Référence CVE CVE-2026-31656 https://www.cve.org/CVERecord?id=CVE-2026-31656 Référence CVE CVE-2026-31658 https://www.cve.org/CVERecord?id=CVE-2026-31658 Référence CVE CVE-2026-31660 https://www.cve.org/CVERecord?id=CVE-2026-31660 Référence CVE CVE-2026-31661 https://www.cve.org/CVERecord?id=CVE-2026-31661 Référence CVE CVE-2026-31662 https://www.cve.org/CVERecord?id=CVE-2026-31662 Référence CVE CVE-2026-31664 https://www.cve.org/CVERecord?id=CVE-2026-31664 Référence CVE CVE-2026-31665 https://www.cve.org/CVERecord?id=CVE-2026-31665 Référence CVE CVE-2026-31667 https://www.cve.org/CVERecord?id=CVE-2026-31667 Référence CVE CVE-2026-31670 https://www.cve.org/CVERecord?id=CVE-2026-31670 Référence CVE CVE-2026-31671 https://www.cve.org/CVERecord?id=CVE-2026-31671 Référence CVE CVE-2026-31672 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31646 Référence CVE CVE-2026-31648 https://www.cve.org/CVERecord?id=CVE-2026-31648 Référence CVE CVE-2026-31649 https://www.cve.org/CVERecord?id=CVE-2026-31649 Référence CVE CVE-2026-31651 https://www.cve.org/CVERecord?id=CVE-2026-31651 Référence CVE CVE-2026-31655 https://www.cve.org/CVERecord?id=CVE-2026-31655 Référence CVE CVE-2026-31656 https://www.cve.org/CVERecord?id=CVE-2026-31656 Référence CVE CVE-2026-31657 https://www.cve.org/CVERecord?id=CVE-2026-31657 Référence CVE CVE-2026-31658 https://www.cve.org/CVERecord?id=CVE-2026-31658 Référence CVE CVE-2026-31659 https://www.cve.org/CVERecord?id=CVE-2026-31659 Référence CVE CVE-2026-31660 https://www.cve.org/CVERecord?id=CVE-2026-31660 Référence CVE CVE-2026-31661 https://www.cve.org/CVERecord?id=CVE-2026-31661 Référence CVE CVE-2026-31662 https://www.cve.org/CVERecord?id=CVE-2026-31662 Référence CVE CVE-2026-31664 https://www.cve.org/CVERecord?id=CVE-2026-31664 Référence CVE CVE-2026-31665 https://www.cve.org/CVERecord?id=CVE-2026-31665 Référence CVE CVE-2026-31667 https://www.cve.org/CVERecord?id=CVE-2026-31667 Référence CVE CVE-2026-31668 https://www.cve.org/CVERecord?id=CVE-2026-31668 Référence CVE CVE-2026-31669 https://www.cve.org/CVERecord?id=CVE-2026-31669 Référence CVE CVE-2026-31670 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31624 Référence CVE CVE-2026-31625 https://www.cve.org/CVERecord?id=CVE-2026-31625 Référence CVE CVE-2026-31626 https://www.cve.org/CVERecord?id=CVE-2026-31626 Référence CVE CVE-2026-31627 https://www.cve.org/CVERecord?id=CVE-2026-31627 Référence CVE CVE-2026-31646 https://www.cve.org/CVERecord?id=CVE-2026-31646 Référence CVE CVE-2026-31647 https://www.cve.org/CVERecord?id=CVE-2026-31647 Référence CVE CVE-2026-31651 https://www.cve.org/CVERecord?id=CVE-2026-31651 Référence CVE CVE-2026-31657 https://www.cve.org/CVERecord?id=CVE-2026-31657 Référence CVE CVE-2026-31659 https://www.cve.org/CVERecord?id=CVE-2026-31659 Référence CVE CVE-2026-31660 https://www.cve.org/CVERecord?id=CVE-2026-31660 Référence CVE CVE-2026-31661 https://www.cve.org/CVERecord?id=CVE-2026-31661 Référence CVE CVE-2026-31663 https://www.cve.org/CVERecord?id=CVE-2026-31663 Référence CVE CVE-2026-31664 https://www.cve.org/CVERecord?id=CVE-2026-31664 Référence CVE CVE-2026-31665 https://www.cve.org/CVERecord?id=CVE-2026-31665 Référence CVE CVE-2026-31667 https://www.cve.org/CVERecord?id=CVE-2026-31667 Référence CVE CVE-2026-31670 https://www.cve.org/CVERecord?id=CVE-2026-31670 Référence CVE CVE-2026-31672 https://www.cve.org/CVERecord?id=CVE-2026-31672 Référence CVE CVE-2026-31673 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31646 Référence CVE CVE-2026-31648 https://www.cve.org/CVERecord?id=CVE-2026-31648 Référence CVE CVE-2026-31649 https://www.cve.org/CVERecord?id=CVE-2026-31649 Référence CVE CVE-2026-31651 https://www.cve.org/CVERecord?id=CVE-2026-31651 Référence CVE CVE-2026-31655 https://www.cve.org/CVERecord?id=CVE-2026-31655 Référence CVE CVE-2026-31656 https://www.cve.org/CVERecord?id=CVE-2026-31656 Référence CVE CVE-2026-31657 https://www.cve.org/CVERecord?id=CVE-2026-31657 Référence CVE CVE-2026-31658 https://www.cve.org/CVERecord?id=CVE-2026-31658 Référence CVE CVE-2026-31659 https://www.cve.org/CVERecord?id=CVE-2026-31659 Référence CVE CVE-2026-31660 https://www.cve.org/CVERecord?id=CVE-2026-31660 Référence CVE CVE-2026-31661 https://www.cve.org/CVERecord?id=CVE-2026-31661 Référence CVE CVE-2026-31662 https://www.cve.org/CVERecord?id=CVE-2026-31662 Référence CVE CVE-2026-31664 https://www.cve.org/CVERecord?id=CVE-2026-31664 Référence CVE CVE-2026-31665 https://www.cve.org/CVERecord?id=CVE-2026-31665 Référence CVE CVE-2026-31667 https://www.cve.org/CVERecord?id=CVE-2026-31667 Référence CVE CVE-2026-31668 https://www.cve.org/CVERecord?id=CVE-2026-31668 Référence CVE CVE-2026-31669 https://www.cve.org/CVERecord?id=CVE-2026-31669 Référence CVE CVE-2026-31670 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31550 Référence CVE CVE-2026-31552 https://www.cve.org/CVERecord?id=CVE-2026-31552 Référence CVE CVE-2026-31555 https://www.cve.org/CVERecord?id=CVE-2026-31555 Référence CVE CVE-2026-31570 https://www.cve.org/CVERecord?id=CVE-2026-31570 Référence CVE CVE-2026-31628 https://www.cve.org/CVERecord?id=CVE-2026-31628 Référence CVE CVE-2026-31649 https://www.cve.org/CVERecord?id=CVE-2026-31649 Référence CVE CVE-2026-31651 https://www.cve.org/CVERecord?id=CVE-2026-31651 Référence CVE CVE-2026-31658 https://www.cve.org/CVERecord?id=CVE-2026-31658 Référence CVE CVE-2026-31659 https://www.cve.org/CVERecord?id=CVE-2026-31659 Référence CVE CVE-2026-31660 https://www.cve.org/CVERecord?id=CVE-2026-31660 Référence CVE CVE-2026-31661 https://www.cve.org/CVERecord?id=CVE-2026-31661 Référence CVE CVE-2026-31662 https://www.cve.org/CVERecord?id=CVE-2026-31662 Référence CVE CVE-2026-31665 https://www.cve.org/CVERecord?id=CVE-2026-31665 Référence CVE CVE-2026-31667 https://www.cve.org/CVERecord?id=CVE-2026-31667 Référence CVE CVE-2026-31668 https://www.cve.org/CVERecord?id=CVE-2026-31668 Référence CVE CVE-2026-31670 https://www.cve.org/CVERecord?id=CVE-2026-31670 Référence CVE CVE-2026-31671 https://www.cve.org/CVERecord?id=CVE-2026-31671 Référence CVE CVE-2026-31672 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31570 Référence CVE CVE-2026-31628 https://www.cve.org/CVERecord?id=CVE-2026-31628 Référence CVE CVE-2026-31634 https://www.cve.org/CVERecord?id=CVE-2026-31634 Référence CVE CVE-2026-31649 https://www.cve.org/CVERecord?id=CVE-2026-31649 Référence CVE CVE-2026-31651 https://www.cve.org/CVERecord?id=CVE-2026-31651 Référence CVE CVE-2026-31656 https://www.cve.org/CVERecord?id=CVE-2026-31656 Référence CVE CVE-2026-31657 https://www.cve.org/CVERecord?id=CVE-2026-31657 Référence CVE CVE-2026-31658 https://www.cve.org/CVERecord?id=CVE-2026-31658 Référence CVE CVE-2026-31659 https://www.cve.org/CVERecord?id=CVE-2026-31659 Référence CVE CVE-2026-31660 https://www.cve.org/CVERecord?id=CVE-2026-31660 Référence CVE CVE-2026-31661 https://www.cve.org/CVERecord?id=CVE-2026-31661 Référence CVE CVE-2026-31662 https://www.cve.org/CVERecord?id=CVE-2026-31662 Référence CVE CVE-2026-31664 https://www.cve.org/CVERecord?id=CVE-2026-31664 Référence CVE CVE-2026-31665 https://www.cve.org/CVERecord?id=CVE-2026-31665 Référence CVE CVE-2026-31667 https://www.cve.org/CVERecord?id=CVE-2026-31667 Référence CVE CVE-2026-31668 https://www.cve.org/CVERecord?id=CVE-2026-31668 Référence CVE CVE-2026-31669 https://www.cve.org/CVERecord?id=CVE-2026-31669 Référence CVE CVE-2026-31670 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31647 Référence CVE CVE-2026-31648 https://www.cve.org/CVERecord?id=CVE-2026-31648 Référence CVE CVE-2026-31649 https://www.cve.org/CVERecord?id=CVE-2026-31649 Référence CVE CVE-2026-31651 https://www.cve.org/CVERecord?id=CVE-2026-31651 Référence CVE CVE-2026-31655 https://www.cve.org/CVERecord?id=CVE-2026-31655 Référence CVE CVE-2026-31656 https://www.cve.org/CVERecord?id=CVE-2026-31656 Référence CVE CVE-2026-31657 https://www.cve.org/CVERecord?id=CVE-2026-31657 Référence CVE CVE-2026-31658 https://www.cve.org/CVERecord?id=CVE-2026-31658 Référence CVE CVE-2026-31659 https://www.cve.org/CVERecord?id=CVE-2026-31659 Référence CVE CVE-2026-31660 https://www.cve.org/CVERecord?id=CVE-2026-31660 Référence CVE CVE-2026-31661 https://www.cve.org/CVERecord?id=CVE-2026-31661 Référence CVE CVE-2026-31662 https://www.cve.org/CVERecord?id=CVE-2026-31662 Référence CVE CVE-2026-31664 https://www.cve.org/CVERecord?id=CVE-2026-31664 Référence CVE CVE-2026-31665 https://www.cve.org/CVERecord?id=CVE-2026-31665 Référence CVE CVE-2026-31666 https://www.cve.org/CVERecord?id=CVE-2026-31666 Référence CVE CVE-2026-31667 https://www.cve.org/CVERecord?id=CVE-2026-31667 Référence CVE CVE-2026-31668 https://www.cve.org/CVERecord?id=CVE-2026-31668 Référence CVE CVE-2026-31669 https://www.cve.org/CVERecord?id=

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

sécurité Microsoft CVE-2026-31639 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31642 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31646 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31649 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31651 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31655 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31656 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31657 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31658 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31659 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31660 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31662 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31664 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31665 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31667 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31668 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31669 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31670 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31671 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31672 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31673 du 26 avril 2026 Bu

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-013627LinuxのLinux Kernelにおける不特定の脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。nfc: pn533における、バイトを消費する前に受信用skbを割り当てる問題です。pn532_receive_buf()は受け入れたバイト数をserdevコアに報告します。現在のコードはrecv_skbにバイトを消費させた後、まだ新しい受信バッファを割り当てる前にpn533_recv_frame()に完全なフレームを渡している可能性があります。もしalloc_skb()が失敗した場合、コールバックはすでにバイトを消費しているにもかかわらず0を返し、次の受信コールバックのためにrecv_skbをNULLのままにします。これによりreceive_buf()の会計契約が破られ、次のskb_put_u8()でNULL参照が発生する可能性があります。次のバイトを消費する前に受信用skbを遅延割り当てし、割り当てに失敗した場合はすでに受け入れたバイト数を返すようにしています。

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: < 5.5, 5.10.253 ≤ 5.10.*, 5.15.203 ≤ 5.15.*, 6.1.169 ≤ 6.1.*, 6.6.135 ≤ 6.6.*, 6.12.82 ≤ 6.12.*, 6.18.23 ≤ 6.18.*, 6.19.13 ≤ 6.19.*, 7.0 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 24 Apr 2026 · Last source change 11 May 2026, 22:13 UTC · CWE not yet assigned

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-2026-25553
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD enriched

Missing structured fields: CWE classification. 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-2026-25553↗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-2026-31660 · cve.blacktree.nl