CVE-2024-27015 | 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.
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.
- 🔗 git.kernel.org/stable/c/e719b52d0c56989b0f3475a03a6d64f1…
- 🔗 git.kernel.org/stable/c/f1c3c61701a0b12f4906152c1626a5de…
- 🔗 git.kernel.org/stable/c/4ed82dd368ad883dc4284292937b882f…
- 🔗 git.kernel.org/stable/c/e3f078103421642fcd5f05c5e70777fe…
- 🔗 git.kernel.org/stable/c/6db5dc7b351b9569940cd1cf445e237c…
- 🔗 lists.fedoraproject.org/archives/list/[email protected]…
- 🔗 lists.fedoraproject.org/archives/list/[email protected]…
- 🔗 lists.fedoraproject.org/archives/list/[email protected]…
Zero-Day & Vulnerability Intelligence Hub
Echtzeit-Tracking mit EPSS Exploit-Wahrscheinlichkeiten, Angriffsvektor-Decodern und KI-Patch-Anleitungen.
📊 Historien-Charts — Criticals-Trend · Vendors · EPSS-Verteilung
| Tier | 2026-08-29 | 2026-09-06 |
|---|---|---|
| ≥90 % | 4 | 0 |
| ≥50 % | 4 | 0 |
| ≥10 % | 3 | 0 |
| <10 % | 304 | 300 |
CVE-2024-27015 | 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.
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 netwo