Scantide
Live local intelligence
2026-10-17 21:56 CEST · Intelligence refreshed (Europe/Stockholm)

Understand software risk,
with the evidence visible.

Search software, operating systems, packages, CVEs, KBs, campaigns, advisories, named operations or GHSAs and review correlated vulnerability, campaign, advisory, exploitation, update, affected-product and lifecycle intelligence in one place.

Vendor and product names are suggested from the active PostgreSQL intelligence index as you type. Choose Campaign / advisory for named operations such as BADBOX, BADBOX 2.0, NotPetya or ransomware campaigns. Exact product excludes fuzzy identities; Vendor search discovers manufacturer-linked records. Auto detect still recognizes structured IDs such as CVEs, KBs, GHSAs and FLASH/CERT identifiers.
Latest synchronized CVE
CVSS 4.3 Published 2026-10-17 21:00 CEST
Vendor
Affected products
1 affected products/devices 1 software
General vulnerability query Recent High & critical CVEs

Query the vulnerability time window. Default 7 days; narrow to the last 24 hours or expand to 14 or 30 days when needed.

CVSS 9.3/10 Critical severity

First published: 15 October 2026, 14:19 CEST · Last modified: 17 October 2026, 13:14 CEST

CVE lookup — correlated security and lifecycle intelligence

· 7 sources correlated

Critical severity — prioritize remediation

ipv4: validate checksum_start before completing checksum

SeverityCVSS 9.3Critical · Local access
ExploitationNone reportedEPSS 0.2% chance in 30 days
Affected products22 products10 OS · 12 softwareEvidence7 sourcesindependent intelligence collections

Why this rating

  • Rated critical (CVSS 9.3); no exploitation is reported in current sources.

What to do

  1. Check your inventory against the 22 affected products — start with internet-facing systems.
Vendor
Affected products
,
,
,
,
+8 more

Affected products (examples)

Click to open the full list
Linux Linuxgitsemver5.10.*5.15.*6.1.*6.6.*All 22 →

What the vulnerability is

In the Linux kernel, the following vulnerability has been resolved: ipv4: validate checksum_start before completing checksum If a packet with bad checksum metadata gets into the ipv4 stack, skb_checksum_help can corrupt the network header and cause a bunch of mischief. This was discovered and reported by Paulos, and has been reporoduced by others independently since. We really shouldn't allow such packets in, but as a defence in depth measure, let's also check before we complete the checksum. A more complete valid…

Detailed evidence Everything below supports the summary above. Open only what you need.

Matched intelligence coverage 7 sources
EUVD Vulnrichment OSV EPSS CIRCL CVE Affected Products
Cross-source correlations 7 matched lanes

Direct intelligence-source relationships

Direct intelligence-source lanes: every lane below has direct evidence for

in that Scantide intelligence collection. Lanes share the CVE as their join key; their presence together does not imply that one source explicitly referenced another source's record.

7 matched source lanes
ENISA EUVD CISA Vulnrichment OSV EPSS CIRCL OSINT CVE / NVD catalog Affected products/devices · 22
Downstream affected vendors 1 vendors

Affected vendor/product relationships

These vendors are derived from affected product/device evidence tied to this CVE. This is intentionally separate from the direct intelligence-source lanes above: a vendor can have affected products without Scantide having a vendor-specific advisory or Microsoft KB record for the CVE.

 1 affected vendors represented

Affected software, operating systems, hardware and devices 22

Deduplicated across Scantide's structured CVE, NVD applicability, CSAF, vendor advisory, campaign and downstream product evidence. Taxonomy IDs and evidence-only identifiers are excluded from the asset count. Counts represent relationships Scantide can currently prove, not the theoretical maximum downstream ecosystem.

10Operating systems
12Software / applications
NVD/CVE catalog 1CISA Vulnrichment 20Osv 4
Expand all affected categories (22) How can this affect my environment?
Operating systems and platforms (10 — click to show all)
Vendor: Linux
Operating systems and platforms Affected range: All listed or unspecified versions Product-associated Assertion
Primary: NVD/CVE catalogCorroborated: CISA VulnrichmentCorroborated: Osvhigh confidence
Vendor: Linux
Operating systems and platforms Affected range: version f43798c27684ab925adde7d8acc34c78c6e50df8 — before a464d950f31c89565cbaae038cc60db04fe01956 Product-associated Assertion
Primary: CISA Vulnrichment — structured affected recordhigh confidence
Vendor: Linux
Operating systems and platforms Affected range: version f43798c27684ab925adde7d8acc34c78c6e50df8 — before 0fab003ef4698e0628060a45a48f14b43ba2a40a Product-associated Assertion
Primary: CISA Vulnrichment — structured affected recordhigh confidence
Vendor: Linux
Operating systems and platforms Affected range: version f43798c27684ab925adde7d8acc34c78c6e50df8 — before 94524b7b32691de2e2ce162c04d6cbc9106e5cbf Product-associated Assertion
Primary: CISA Vulnrichment — structured affected recordhigh confidence
Vendor: Linux
Operating systems and platforms Affected range: version f43798c27684ab925adde7d8acc34c78c6e50df8 — before a65f69e0f38ffbed1b128029e09097436416dc8b Product-associated Assertion
Primary: CISA Vulnrichment — structured affected recordhigh confidence
Vendor: Linux
Operating systems and platforms Affected range: version f43798c27684ab925adde7d8acc34c78c6e50df8 — before 32a8b0adaa18e52aaa0b246b5ffe683075354dbb Product-associated Assertion
Primary: CISA Vulnrichment — structured affected recordhigh confidence
Vendor: Linux
Operating systems and platforms Affected range: version f43798c27684ab925adde7d8acc34c78c6e50df8 — before f3e835af6226f1dd12160cbd696081e9b6155de0 Product-associated Assertion
Primary: CISA Vulnrichment — structured affected recordhigh confidence
Vendor: Linux
Operating systems and platforms Affected range: version f43798c27684ab925adde7d8acc34c78c6e50df8 — before c3e33464746166264334641dc850a36eef7e6326 Product-associated Assertion
Primary: CISA Vulnrichment — structured affected recordhigh confidence
Vendor: Linux
Operating systems and platforms Affected range: version f43798c27684ab925adde7d8acc34c78c6e50df8 — before 6785011f8b16abf40b1e9d8b2e332232b3e68822 Product-associated Assertion
Primary: CISA Vulnrichment — structured affected recordhigh confidence
Vendor: Linux
Operating systems and platforms Affected range: version 2.6.27 Product-associated Assertion
Primary: CISA Vulnrichment — structured affected recordhigh confidence
Software (12 — click to show all)
Vendor: Not identified in correlated evidence
Software Affected range: All listed or unspecified versions Product-associated Assertion
Primary: CISA VulnrichmentCorroborated: Osvmedium-high confidence
Vendor: Not identified in correlated evidence
Software Affected range: All listed or unspecified versions Product-associated Assertion
Primary: CISA Vulnrichmentmedium-high confidence
Vendor: Not identified in correlated evidence
Software Affected range: All listed or unspecified versions Product-associated Assertion
Primary: CISA Vulnrichmentmedium-high confidence
Vendor: Not identified in correlated evidence
Software Affected range: All listed or unspecified versions Product-associated Assertion
Primary: CISA Vulnrichmentmedium-high confidence
Vendor: Not identified in correlated evidence
Software Affected range: All listed or unspecified versions Product-associated Assertion
Primary: CISA Vulnrichmentmedium-high confidence
Vendor: Not identified in correlated evidence
Software Affected range: All listed or unspecified versions Product-associated Assertion
Primary: CISA Vulnrichmentmedium-high confidence
Vendor: Not identified in correlated evidence
Software Affected range: All listed or unspecified versions Product-associated Assertion
Primary: CISA Vulnrichmentmedium-high confidence
Vendor: Not identified in correlated evidence
Software Affected range: All listed or unspecified versions Product-associated Assertion
Primary: CISA Vulnrichmentmedium-high confidence
Vendor: Not identified in correlated evidence
Software Affected range: All listed or unspecified versions Product-associated Assertion
Primary: CISA Vulnrichmentmedium-high confidence
Vendor: Not identified in correlated evidence
Software Affected range: All listed or unspecified versions Product-associated Assertion
Primary: CISA Vulnrichmentmedium-high confidence
Vendor: Not identified in correlated evidence
Software Affected range: All listed or unspecified versions Product-associated Assertion
Primary: Osv — structured affected recordCorroborated: Osvhigh confidence
Vendor: Not identified in correlated evidence
Software Affected range: All listed or unspecified versions Product-associated Assertion
Primary: Osvmedium-high confidence
What each source says 4
European vulnerability intelligence: ENISA EUVD cross-reference: EUVD-2026-102044.
Exploit probability: Estimated exploitation probability 0.21% — percentile 10.6%.
Vulnerability summary: ipv4: validate checksum_start before completing checksum
CIRCL OSINT observations: 2 CIRCL OSINT references found. Retrieved types: 2 sighting.
OSV advisories 1
ipv4: validate checksum_start before completing checksum
OSV
CVE-2026-99999 Published 2026-10-15T12:19:22.784Z Updated 2026-10-17T02:48:34.229912779Z

In the Linux kernel, the following vulnerability has been resolved: ipv4: validate checksum_start before completing checksum If a packet with bad checksum metadata gets into the ipv4 stack, skb_checksum_help can corrupt the network header and cause a bunch of mischief. This was discovered and reported by Paulos, and has been reporoduced by others independently since. We really shouldn't allow such packets in, but as a defence in depth measure, let's also check before we complete the checksum. A more complete validation at input is forthcoming, but needs more work.

OSV-CONVERSIONOSV-OUTPUT
Related products
  • Linux / Kernel — ECOSYSTEM: introduced 2.6.27, fixed 5.10.272 · ECOSYSTEM: introduced 5.11.0, fixed 5.15.223 · ECOSYSTEM: introduced 5.16.0, fixed 6.1.190 · ECOSYSTEM: introduced 6.2.0, fixed 6.6.159 · ECOSYSTEM: introduced 6.7.0, fixed 6.12.113 · ECOSYSTEM: introduced 6.13.0, fixed 6.18.57 · ECOSYSTEM: introduced 6.19.0, fixed 7.2.11
Read full advisory Open source at storage.googleapis.comOpen source at git.kernel.orgOpen GitHub advisory or evidenceOpen source at www.openwall.comOpen source at git.kernel.orgOpen source at git.kernel.org
Evidence coverage

Correlated from multiple vulnerability, exploitation, advisory, package and affected-product intelligence collections.

Technical query coverage · 17 collections queried · 1 CVEs correlated
2026-10-17 21:56 CESTIntelligence refreshed
1unique CVEs queried and enriched
1unique CVEs correlated to this result
1unique advisories correlated
17intelligence collections queried
Affected-product scope: The product/device count is the deduplicated set Scantide can prove from its currently ingested structured records and advisory text. It is not a claim that only those products were affected; component vulnerabilities such as Log4Shell can have a much larger downstream ecosystem. Advisory and vendor references are kept clickable so additional downstream exposure can be followed to the authoritative source.
Coverage note: Scantide correlates multiple public and locally indexed intelligence sources, but no dataset or matching process is complete. Results may omit software, dependencies, affected versions or advisories, and related records do not by themselves prove that a specific installation is vulnerable. Confirm important findings against vendor guidance and the installed product and version.