LiveActive security incident?Get immediate response
CVE Record

CVE-2025-21726: padata: avoid UAF for reorder_work

In the Linux kernel, the following vulnerability has been resolved: padata: avoid UAF for reorder_work Although the previous patch can avoid ps and ps UAF for _do_serial, it can not avoid potential UAF issue for reorder_work. This issue can happen just as below: crypto_request crypto_request crypto_del_alg padata_do_serial ... padata_reorder // processes all remaining // requests then breaks while (1) { if (!padata) break; ... } padata_do_serial // new request added list_add // sees the new request queue_work(reorder_work) padata_reorder queue_work_on(squeue->work) ... <kworker context> padata_serial_worker // completes new request, // no more outstanding // requests crypto_del_alg // free pd <kworker context> invoke_padata_reorder // UAF of pd To avoid UAF for 'reorder_work', get 'pd' ref before put 'reorder_work' into the 'serial_wq' and put 'pd' ref until the 'serial_wq' finish.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2025-21726 is a Linux kernel use-after-free in padata reorder_work. A local authenticated user may be able to trigger kernel memory corruption, with high confidentiality, integrity, and availability impact. The supplied evidence does not show remote exploitation or active attacks, but exposed multi-user Linux systems and appliances should be prioritized.

Executive priority

High priority for Linux estates, especially shared or sensitive infrastructure. This is not evidenced as internet-routable or actively exploited, but kernel use-after-free bugs can have severe business impact if a local attacker gains code execution or data access.

Technical view

The flaw is CWE-416 in Linux padata. A race around padata_do_serial, padata_reorder, serial work queues, and algorithm deletion can leave reorder_work using freed pd state. The upstream fix adds a pd reference before queuing reorder_work and releases it after serial_wq finishes.

Likely exposure

Exposure is likely on systems running affected Linux kernel versions or vendor kernels without the stable backport. Highest concern is shared Linux hosts, containers relying on host kernels, and products tracking vulnerable kernel branches. Siemens and Debian references indicate downstream vendor relevance, but exact affected product scope must be confirmed there.

Exploitation context

CVSS indicates local attack vector, low complexity, low privileges, and no user interaction. The source bundle marks KEV as false, and no supplied source states active exploitation. Treat this as a local privilege or kernel-compromise risk until vendor guidance narrows practical exploitability.

Researcher notes

Focus review on padata reorder_work lifetime handling and whether downstream kernels carry the pd reference fix. Do not assume all products using Linux are affected; confirm exact vendor kernel branches and advisory mappings. Evidence is strongest for the upstream kernel issue and referenced stable fixes.

Mitigation direction

  • Apply vendor kernel updates containing the referenced stable fixes or backports.
  • Review Debian LTS advisories if using affected Debian kernel packages.
  • Review Siemens SSA-265688 for affected Siemens product status and remediation.
  • Prioritize patching multi-user systems and high-value Linux infrastructure.
  • If no vendor package exists, track vendor guidance before changing kernels manually.

Validation and detection

  • Inventory running kernel versions across Linux servers, appliances, and container hosts.
  • Map each kernel to vendor advisories or referenced stable commits.
  • Confirm whether downstream packages include the reorder_work reference-count fix.
  • Check vulnerability scanners for CVE-2025-21726 coverage and validate manually.
  • Document exceptions where vendor product exposure is not yet confirmed.
Prepared
Confidence
high
Sources
12

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-416: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-21726 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
3ADP providers
11Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2025-21726Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
CVECVE Program Container
siemens-SADPADP container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxbbefa1dd6a6d53537c11624752219e39959d04fb, bbefa1dd6a6d53537c11624752219e39959d04fb, bbefa1dd6a6d53537c11624752219e39959d04fb, bbefa1dd6a6d53537c11624752219e39959d04fb, bbefa1dd6a6d53537c11624752219e39959d04fb, bbefa1dd6a6d53537c11624752219e39959d04fb, bbefa1dd6a6d53537c11624752219e39959d04fb, b4c8ed0bf977760a206997b6429a7ac91978f440, e43d65719527043f1ef79ecba9d4ede58cbc7ffe, 5.4.19, 5.5.3unaffected
LinuxLinux5.6, 0, 5.10.235, 5.15.179, 6.1.129, 6.6.76, 6.12.13, 6.13.2, 6.14affected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-416 · source CWE mapping

Use After Free

Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.