In the Linux kernel, the following vulnerability has been resolved:
rxrpc: Fix untrusted unsigned subtract
Fix the following Smatch static checker warning:
net/rxrpc/rxgk_app.c:65 rxgk_yfs_decode_ticket()
warn: untrusted unsigned subtract. 'ticket_len - 10 * 4'
by prechecking the length of what we're trying to extract in two places in
the token and decoding for a response packet.
Also use sizeof() on the struct we're extracting rather specifying the size
numerically to be consistent with the other related statements.
Security readout for executives and security teams
Plain-English summary
A Linux kernel RxRPC parsing flaw can mishandle an untrusted, undersized ticket or response length. The resulting unsigned arithmetic error may disrupt affected systems. Available evidence supports an availability risk, not data theft or modification.
Executive priority
Treat as a high-priority availability issue for network-exposed systems using the affected kernel functionality. Accelerate vendor patch review and exposure validation, but do not characterize it as actively exploited based on current evidence.
Technical view
The rxgk YFS decoder subtracts fixed field sizes from attacker-influenced unsigned lengths without first confirming sufficient data. This can underflow during ticket and response decoding. The kernel fix adds two length prechecks and replaces a numeric structure length with sizeof().
Likely exposure
The supplied record marks Linux kernel versions beginning with 6.16 and extending toward 6.17 as affected. Practical exposure depends on whether a distribution kernel includes the vulnerable RxRPC code and whether relevant RxRPC/rxgk functionality processes untrusted network input.
Exploitation context
The CVSS vector describes network reachability, low complexity, no privileges, and no user interaction, with availability as the identified impact. The CVE is not in KEV, and the supplied sources provide no evidence of active exploitation or a public exploit.
Researcher notes
The central defect is insufficient bounds validation before unsigned subtraction in rxgk_yfs_decode_ticket(). The stated remediation covers two extraction points during token and response decoding. The supplied version data is not detailed enough to map every distribution kernel reliably; use vendor backport information or commit presence.
Mitigation direction
Apply a vendor-supported kernel update containing the referenced stable fixes.
Prioritize systems using RxRPC or rxgk with untrusted network exposure.
If updating is delayed, consult distribution guidance for supported temporary mitigations.
Restrict unnecessary network access to relevant services where operationally feasible.
Validation and detection
Inventory kernel versions and distribution package revisions across potentially exposed systems.
Confirm whether vendor kernels contain either referenced stable fix.
Verify updated systems boot and run the intended kernel package.
Test relevant RxRPC workloads for normal operation after updating.
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.
description · low confidence lookup
Credential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
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
0ADP providers
3Source links
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.