LiveActive security incident?Get immediate response
CVE Record

CVE-2024-27015: netfilter: flowtable: incorrect pppoe tuple

In the Linux kernel, the following vulnerability has been resolved: netfilter: flowtable: incorrect pppoe tuple pppoe traffic reaching ingress path does not match the flowtable entry because the pppoe header is expected to be at the network header offset. This bug causes a mismatch in the flow table lookup, so pppoe packets enter the classical forwarding path.

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

Security readout for executives and security teams

Plain-English summary

CVE-2024-27015 is a Linux kernel netfilter flowtable bug affecting PPPoE forwarding behavior. The source describes packets failing to match the expected flowtable entry and falling back to the normal forwarding path. Evidence points to a correctness and potential performance/offload issue, not a proven data theft or remote takeover issue.

Executive priority

Treat this as targeted operational risk for PPPoE network infrastructure, not a broad emergency from the provided evidence. Patch during the next controlled kernel maintenance window, sooner for high-throughput gateways that depend on flowtable acceleration.

Technical view

The flaw is in netfilter flowtable PPPoE tuple handling. PPPoE ingress packets are looked up with the PPPoE header expected at the network header offset, causing tuple mismatch and bypass of the flowtable fast path. Linux stable commits and Fedora kernel announcements are referenced as fixes or downstream updates.

Likely exposure

Exposure is most likely on Linux systems acting as routers, gateways, or network appliances that use netfilter flowtables with PPPoE traffic. General Linux servers without PPPoE forwarding or flowtable usage are less likely to be materially affected, based on the provided description.

Exploitation context

The provided sources do not show active exploitation, KEV listing, public exploit activity, CVSS, or CWE data. The described behavior is packet-processing misclassification that sends traffic to classical forwarding, so business impact depends on whether affected systems rely on flowtable acceleration for PPPoE.

Researcher notes

The record lacks CVSS, CWE, exploit status, and detailed affected-version semantics. The core evidence is the kernel resolution text and stable commit references. Analysis should stay focused on PPPoE flowtable tuple mismatch and avoid expanding impact beyond forwarding-path correctness without vendor confirmation.

Mitigation direction

  • Update affected Linux kernels through vendor-supported packages or stable releases.
  • Prioritize PPPoE routers, gateways, firewalls, and network appliances using netfilter flowtables.
  • Review Fedora and Linux stable advisories for applicable fixed kernel builds.
  • If using another distribution, check its kernel advisory for backported fixes.
  • Avoid direct deploy shortcuts; follow normal kernel change and reboot procedures.

Validation and detection

  • Inventory Linux systems that route PPPoE traffic with netfilter flowtables enabled.
  • Compare running kernel versions against vendor advisories and referenced stable fixes.
  • Confirm installed kernel packages include the CVE-2024-27015 fix or equivalent backport.
  • After updating, verify PPPoE forwarding still works as expected.
  • Monitor performance counters or operational telemetry for forwarding-path regressions.
Prepared
Confidence
medium
Sources
10

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-2024-27015 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
9Source 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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux72efd585f7144a047f7da63864284764596ccad9, 72efd585f7144a047f7da63864284764596ccad9, 72efd585f7144a047f7da63864284764596ccad9, 72efd585f7144a047f7da63864284764596ccad9, 72efd585f7144a047f7da63864284764596ccad9unaffected
LinuxLinux5.13, 0, 5.15.157, 6.1.88, 6.6.29, 6.8.8, 6.9affected
Weakness

CWE details

No CWE listed

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