LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23118: rxrpc: Fix data-race warning and potential load/store tearing

In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix data-race warning and potential load/store tearing Fix the following: BUG: KCSAN: data-race in rxrpc_peer_keepalive_worker / rxrpc_send_data_packet which is reporting an issue with the reads and writes to ->last_tx_at in: conn->peer->last_tx_at = ktime_get_seconds(); and: keepalive_at = peer->last_tx_at + RXRPC_KEEPALIVE_TIME; The lockless accesses to these to values aren't actually a problem as the read only needs an approximate time of last transmission for the purposes of deciding whether or not the transmission of a keepalive packet is warranted yet. Also, as ->last_tx_at is a 64-bit value, tearing can occur on a 32-bit arch. Fix both of these by switching to an unsigned int for ->last_tx_at and only storing the LSW of the time64_t. It can then be reconstructed at need provided no more than 68 years has elapsed since the last transmission.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2026-23118 is a Linux kernel rxrpc bug involving a timing field used for keepalive decisions. The source describes a data-race warning and possible 64-bit value tearing on 32-bit systems. No public source in the bundle assigns a CVSS score or states active exploitation.

Executive priority

Treat this as a tracked kernel maintenance item, not an emergency based on current evidence. Escalate priority for affected 32-bit Linux systems or environments that rely on rxrpc once vendor advisories confirm exposure.

Technical view

The rxrpc peer last_tx_at field was accessed locklessly by transmit and keepalive code. The kernel note says approximate reads are acceptable for keepalive timing, but 64-bit tearing can occur on 32-bit architectures. The fix stores the least significant word as an unsigned int and reconstructs time when needed.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions where rxrpc code is present or used. The bundle lists affected Linux versions including 4.17, 6.6.130, 6.12.69, 6.18.8, and 6.19, but distro-specific impact is not provided.

Exploitation context

The provided sources do not show active exploitation, proof-of-concept activity, KEV listing, or a defined attacker path. The described issue is a race/tearing correctness flaw in kernel rxrpc keepalive timing rather than a clearly documented remote compromise primitive.

Researcher notes

The source explicitly says the lockless approximate timing read is not itself a problem, but 64-bit tearing on 32-bit architectures is. No CVSS, CWE, concrete impact, or exploitation evidence is included, so impact assessment remains constrained.

Mitigation direction

  • Apply vendor kernel updates that include the referenced stable fixes.
  • Check Linux distribution advisories for package-specific affected and fixed versions.
  • Prioritize systems that use rxrpc or run affected 32-bit kernels.
  • Keep normal kernel patch management moving if rxrpc exposure is uncertain.

Validation and detection

  • Inventory Linux kernel versions across affected assets.
  • Confirm whether rxrpc is built, loaded, or operationally required.
  • Verify fixed kernels include one of the referenced stable commits.
  • Review vendor advisories for your exact distribution and kernel package.
Prepared
Confidence
medium
Sources
6

Public sources used

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.

cve · low confidence lookup

CVE-2026-23118 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
3Timeline events
0ADP providers
5Source links

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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxace45bec6d77bc061c3c3d8ad99e298ea9800c2b, ace45bec6d77bc061c3c3d8ad99e298ea9800c2b, ace45bec6d77bc061c3c3d8ad99e298ea9800c2b, ace45bec6d77bc061c3c3d8ad99e298ea9800c2bunaffected
LinuxLinux4.17, 0, 6.6.130, 6.12.69, 6.18.8, 6.19affected
Weakness

CWE details

No CWE listed

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