CVE-2019-25160

HIGHNVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2024-02-26. NVD baseline CVSS 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 7.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

netlabel: fix out-of-bounds memory accesses

There are two array out-of-bounds memory accesses, one in cipso_v4_map_lvl_valid(), the other in netlbl_bitmap_walk(). Both errors are embarassingly simple, and the fixes are straightforward.

As a FYI for anyone backporting this patch to kernels prior to v4.8, you'll want to apply the netlbl_bitmap_walk() patch to cipso_v4_bitmap_walk() as netlbl_bitmap_walk() doesn't exist before Linux v4.8.

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
32
EG Risk 32/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity71% × 45%
Exploitation1% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.8%
EPSS %ILE
53rd
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

February 26, 2024

Last Modified

August 5, 2026

Advisory Details (8)

Auto-updated Aug 5, 2026
Patch available.
generic

netlabel: fix out-of-bounds memory accesses - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5578de4834fe0f2a34fedc7374be691443396d1f
generic

netlabel: fix out-of-bounds memory accesses - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fbf9578919d6c91100ec63acf2cba641383f6c78
generic

netlabel: fix out-of-bounds memory accesses - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e3713abc4248aa6bcc11173d754c418b02a62cbb
generic

netlabel: fix out-of-bounds memory accesses - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fcfe700acdc1c72eab231300e82b962bac2b2b2c
generic

netlabel: fix out-of-bounds memory accesses - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1c973f9c7cc2b3caae93192fdc8ecb3f0b4ac000
generic

netlabel: fix out-of-bounds memory accesses - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/dc18101f95fa6e815f426316b8b9a5cee28a334e
generic

netlabel: fix out-of-bounds memory accesses - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c61d01faa5550e06794dcf86125ccd325bfad950
generic

netlabel: fix out-of-bounds memory accesses - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/97bc3683c24999ee621d847c9348c75d2fe86272

Vendor Advisories for CVE-2019-25160(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:4.18.0-147.el82019-11-05redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux—4.19.28-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux—4.19.28-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—4.19.28-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—4.19.28-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 4× in last 7d / 26× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 168 total refreshes for this CVE.

  1. 2026-10-03 14:22 UTCEPSS rescore
  2. 2026-09-30 14:59 UTCEPSS rescore
  3. 2026-09-30 10:18 UTCEG score recompute
  4. 2026-09-28 13:46 UTCEPSS rescore
  5. 2026-09-27 13:40 UTCEPSS rescore
  6. 2026-09-26 20:33 UTCOSV refresh
  7. 2026-09-26 15:54 UTCEPSS rescore
  8. 2026-09-26 15:54 UTCEPSS rescore
  9. 2026-09-26 00:20 UTCEPSS rescore
  10. 2026-09-24 13:59 UTCEPSS rescore
  11. 2026-09-23 13:43 UTCEPSS rescore
  12. 2026-09-22 14:43 UTCEPSS rescore
  13. 2026-09-21 20:28 UTCEPSS rescore
  14. 2026-09-20 20:10 UTCEPSS rescore
  15. 2026-09-18 19:22 UTCEPSS rescore
  16. 2026-09-17 19:22 UTCEPSS rescore
  17. 2026-09-16 14:04 UTCEPSS rescore
  18. 2026-09-15 03:05 UTCEPSS rescore
  19. 2026-09-13 16:42 UTCEPSS rescore
  20. 2026-09-12 14:56 UTCEPSS rescore
  21. 2026-09-11 14:48 UTCEPSS rescore
  22. 2026-09-11 09:32 UTCEPSS rescore
  23. 2026-09-07 15:57 UTCEPSS rescore
  24. 2026-09-07 05:48 UTCOSV refresh
  25. 2026-09-06 13:44 UTCEPSS rescore
Show 75 more
  1. 2026-09-05 15:24 UTCEPSS rescore
  2. 2026-09-04 13:56 UTCEPSS rescore
  3. 2026-09-02 14:07 UTCEPSS rescore
  4. 2026-09-01 03:32 UTCEPSS rescore
  5. 2026-08-30 19:13 UTCEPSS rescore
  6. 2026-08-30 01:18 UTCEPSS rescore
  7. 2026-08-28 21:36 UTCEPSS rescore
  8. 2026-08-27 14:21 UTCEPSS rescore
  9. 2026-08-26 14:42 UTCEPSS rescore
  10. 2026-08-25 13:45 UTCEPSS rescore
  11. 2026-08-24 14:11 UTCEPSS rescore
  12. 2026-08-21 23:45 UTCEPSS rescore
  13. 2026-08-20 22:51 UTCEPSS rescore
  14. 2026-08-20 15:31 UTCOSV refresh
  15. 2026-08-19 17:00 UTCEPSS rescore
  16. 2026-08-18 13:44 UTCEPSS rescore
  17. 2026-08-17 13:43 UTCEPSS rescore
  18. 2026-08-16 14:52 UTCEPSS rescore
  19. 2026-08-16 02:10 UTCEPSS rescore
  20. 2026-08-15 01:26 UTCEPSS rescore
  21. 2026-08-12 13:47 UTCEPSS rescore
  22. 2026-08-09 13:43 UTCEPSS rescore
  23. 2026-08-08 16:33 UTCEPSS rescore
  24. 2026-08-07 16:23 UTCEPSS rescore
  25. 2026-08-06 13:43 UTCEPSS rescore
  26. 2026-08-05 19:13 UTCEPSS rescore
  27. 2026-08-05 09:46 UTCEG score recompute
  28. 2026-08-05 09:46 UTCVendor advisory
  29. 2026-08-05 09:46 UTCGHSA enrichment
  30. 2026-08-04 15:05 UTCEPSS rescore
  31. 2026-08-04 12:23 UTCEG score recompute
  32. 2026-08-04 12:23 UTCVendor advisory
  33. 2026-08-04 12:23 UTCGHSA enrichment
  34. 2026-08-04 09:55 UTCEG score recompute
  35. 2026-08-04 09:55 UTCVendor advisory
  36. 2026-08-04 09:55 UTCGHSA enrichment
  37. 2026-08-02 02:23 UTCEPSS rescore
  38. 2026-08-01 11:36 UTCOSV refresh
  39. 2026-08-01 04:12 UTCEPSS rescore
  40. 2026-07-30 16:24 UTCEPSS rescore
  41. 2026-07-30 01:27 UTCEPSS rescore
  42. 2026-07-28 15:32 UTCEPSS rescore
  43. 2026-07-26 14:51 UTCEPSS rescore
  44. 2026-07-25 14:14 UTCEPSS rescore
  45. 2026-07-24 14:14 UTCEPSS rescore
  46. 2026-07-24 14:14 UTCEPSS rescore
  47. 2026-07-23 14:15 UTCEPSS rescore
  48. 2026-07-23 01:44 UTCEG score recompute
  49. 2026-07-22 22:24 UTCEG score recompute
  50. 2026-07-22 14:05 UTCEPSS rescore
  51. 2026-07-21 15:22 UTCEPSS rescore
  52. 2026-07-21 15:22 UTCEPSS rescore
  53. 2026-07-20 17:04 UTCEPSS rescore
  54. 2026-07-20 17:04 UTCEPSS rescore
  55. 2026-07-19 14:28 UTCEPSS rescore
  56. 2026-07-19 14:28 UTCEPSS rescore
  57. 2026-07-19 02:26 UTCEPSS rescore
  58. 2026-07-19 02:26 UTCEPSS rescore
  59. 2026-07-18 10:01 UTCEPSS rescore
  60. 2026-07-16 16:59 UTCEPSS rescore
  61. 2026-07-16 16:59 UTCEPSS rescore
  62. 2026-07-15 16:55 UTCEPSS rescore
  63. 2026-07-15 16:55 UTCEPSS rescore
  64. 2026-07-14 18:40 UTCOSV refresh
  65. 2026-07-13 22:27 UTCEPSS rescore
  66. 2026-07-13 06:10 UTCEPSS rescore
  67. 2026-07-13 06:10 UTCEPSS rescore
  68. 2026-07-12 05:43 UTCEPSS rescore
  69. 2026-07-12 05:43 UTCEPSS rescore
  70. 2026-07-11 08:24 UTCEPSS rescore
  71. 2026-07-11 08:24 UTCEPSS rescore
  72. 2026-07-09 19:06 UTCEPSS rescore
  73. 2026-07-08 15:11 UTCEPSS rescore
  74. 2026-07-07 13:43 UTCEPSS rescore
  75. 2026-07-06 16:25 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2019-25160?
CVE-2019-25160 is a high vulnerability published on February 26, 2024. In the Linux kernel, the following vulnerability has been resolved: netlabel: fix out-of-bounds memory accesses There are two array out-of-bounds memory accesses, one in cipsov4maplvlvalid(), the other in netlblbitmapwalk(). Both errors are embarassingly simple, and the fixes are straightforward.…
When was CVE-2019-25160 disclosed?
CVE-2019-25160 was first published on February 26, 2024, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-25160 actively exploited?
CVE-2019-25160 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2019-25160?
CVE-2019-25160 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2019-25160?
A fix for CVE-2019-25160 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2019-25160 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2019-25160

Explore →

Is Your Infrastructure Affected by CVE-2019-25160?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs