LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26677: rxrpc: Fix delayed ACKs to not set the reference serial number

In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix delayed ACKs to not set the reference serial number Fix the construction of delayed ACKs to not set the reference serial number as they can't be used as an RTT reference.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2024-26677 is a Linux kernel rxrpc issue in delayed acknowledgment handling. The source says delayed ACKs incorrectly set a reference serial number, which cannot be used for RTT reference. No severity, CVSS, CWE, exploitation, or impact detail is provided, so urgency depends on affected kernel use and vendor guidance.

Executive priority

Handle through normal kernel patch governance unless your environment uses rxrpc-dependent services or exposed Linux infrastructure. The risk is not well quantified from the available sources, but kernel fixes should not be ignored because operational exposure can vary by configuration.

Technical view

The Linux kernel rxrpc subsystem was corrected so delayed ACK construction no longer sets the reference serial number. The CVE record identifies affected Linux kernel version ranges and stable commit references, but does not describe a concrete security impact, attacker prerequisites, crash condition, privilege boundary, or data exposure path.

Likely exposure

Exposure is most likely on Linux systems running affected kernel builds where rxrpc-related functionality is present or enabled. The bundle does not prove that all Linux deployments are practically exposed, and distribution backports may change version-based conclusions.

Exploitation context

The source bundle marks CISA KEV as false and provides no cited evidence of active exploitation or public weaponization. Treat exploitation status as unknown, not active, unless later vendor or KEV evidence says otherwise.

Researcher notes

Evidence is sparse: the CVE describes a protocol ACK construction bug and references upstream stable commits, but does not supply CVSS, CWE, exploitability analysis, or impact mechanics. Researchers should validate against upstream diffs and distribution backports before assigning operational severity.

Mitigation direction

  • Check Linux distribution advisories for CVE-2024-26677 fixed kernel packages.
  • Update affected systems to vendor-supported kernels containing the referenced stable fixes.
  • Prioritize internet-facing or business-critical Linux systems first if affected.
  • If rxrpc is unnecessary, evaluate disabling related functionality through vendor-supported controls.
  • Track vendor guidance because no standalone workaround is named in the bundle.

Validation and detection

  • Inventory Linux kernel versions and map them to vendor CVE advisories.
  • Confirm installed kernels include one of the referenced stable fixes or a vendor backport.
  • Identify whether rxrpc or dependent services are enabled in relevant environments.
  • Review exception cases where affected kernels remain deployed without vendor fixes.
  • Record distribution-specific package status rather than relying only on upstream version numbers.
Prepared
Confidence
medium
Sources
5

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-2024-26677 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
2ADP providers
4Source links

SSVC decision data

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

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
other:ssvc
CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux17926a79320afa9b95df6b977b40cca6d8713cea, 17926a79320afa9b95df6b977b40cca6d8713cea, 17926a79320afa9b95df6b977b40cca6d8713ceaunaffected
LinuxLinux2.6.22, 0, 6.6.17, 6.7.5, 6.8affected
Weakness

CWE details

No CWE listed

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