CVE-2018-12233

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2022-05-14. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 2%CVSS: 7.8Exploit: NoneExposed: 0

A fix is available — apply it.

In the ea_get function in fs/jfs/xattr.c in the Linux kernel through 4.17.1, a memory corruption bug in JFS can be triggered by calling setxattr twice with two different extended attribute names on the same file. This vulnerability can be triggered by an unprivileged user with the ability to create files and execute programs. A kmalloc call is incorrect, leading to slab-out-of-bounds in jfs_xattr.

CVSS v3
7.8
EG Score
7.8(medium)
EPSS
81.6%
KEV
Not listed

Published

June 12, 2018

Last Modified

November 21, 2024

References (24)

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-image-extra-3.13.0-157-generic (3.13.0-157.207) @ trusty2026-05-28ubuntu
ubuntulinux-image-extra-4.4.0-134-generic (4.4.0-134.160~14.04.1) @ trusty2026-05-28ubuntu
ubuntulinux-image-unsigned-4.15.0-33-lowlatency (4.15.0-33.36~16.04.1) @ xenial2026-05-28ubuntu
ubuntulinux-image-unsigned-4.15.0-33-lowlatency (4.15.0-33.36) @ bionic2026-05-28ubuntu
ubuntulinux-image-extra-4.4.0-134-generic (4.4.0-134.160) @ xenial2026-05-28ubuntu
ubuntulinux-image-unsigned-4.15.0-1022-azure (4.15.0-1022.22~16.04.1) @ xenial2026-05-28ubuntu

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.

Weakness Classification(1)

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

All Vendor Advisories

(6)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 13× in last 7d / 49× 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.

  1. 2026-07-07 13:42 UTCEPSS rescore
  2. 2026-07-07 13:42 UTCEPSS rescore
  3. 2026-07-06 16:24 UTCEPSS rescore
  4. 2026-07-06 16:24 UTCEPSS rescore
  5. 2026-07-06 02:20 UTCEPSS rescore
  6. 2026-07-05 02:27 UTCEPSS rescore
  7. 2026-07-04 06:28 UTCEPSS rescore
  8. 2026-07-04 06:26 UTCOSV refresh
  9. 2026-07-02 16:54 UTCEPSS rescore
  10. 2026-07-01 15:03 UTCEPSS rescore
  11. 2026-07-01 15:03 UTCEPSS rescore
  12. 2026-06-30 23:19 UTCEPSS rescore
  13. 2026-06-30 23:19 UTCEPSS rescore
  14. 2026-06-29 14:03 UTCEPSS rescore
  15. 2026-06-28 14:04 UTCEPSS rescore
  16. 2026-06-28 04:53 UTCEPSS rescore
  17. 2026-06-28 04:53 UTCEPSS rescore
  18. 2026-06-27 03:06 UTCEPSS rescore
  19. 2026-06-25 13:47 UTCEPSS rescore
  20. 2026-06-25 13:47 UTCEPSS rescore
  21. 2026-06-24 14:02 UTCEPSS rescore
  22. 2026-06-24 14:02 UTCEPSS rescore
  23. 2026-06-23 21:30 UTCEPSS rescore
  24. 2026-06-22 14:23 UTCEPSS rescore
  25. 2026-06-21 14:54 UTCEPSS rescore
Show 50 more
  1. 2026-06-21 14:54 UTCEPSS rescore
  2. 2026-06-21 01:57 UTCEPSS rescore
  3. 2026-06-21 01:57 UTCEPSS rescore
  4. 2026-06-19 19:23 UTCEPSS rescore
  5. 2026-06-18 17:50 UTCEPSS rescore
  6. 2026-06-18 17:50 UTCEPSS rescore
  7. 2026-06-17 17:50 UTCEPSS rescore
  8. 2026-06-17 17:50 UTCEPSS rescore
  9. 2026-06-16 17:50 UTCEPSS rescore
  10. 2026-06-16 17:50 UTCEPSS rescore
  11. 2026-06-15 18:13 UTCOSV refresh
  12. 2026-06-15 17:45 UTCEPSS rescore
  13. 2026-06-14 23:14 UTCEPSS rescore
  14. 2026-06-14 23:14 UTCEPSS rescore
  15. 2026-06-13 22:58 UTCEPSS rescore
  16. 2026-06-13 22:58 UTCEPSS rescore
  17. 2026-06-12 23:09 UTCEPSS rescore
  18. 2026-06-11 13:57 UTCEPSS rescore
  19. 2026-06-10 22:16 UTCEPSS rescore
  20. 2026-06-10 13:19 UTCEPSS rescore
  21. 2026-06-08 14:14 UTCEPSS rescore
  22. 2026-06-08 14:14 UTCEPSS rescore
  23. 2026-06-07 15:22 UTCEPSS rescore
  24. 2026-06-07 15:22 UTCEPSS rescore
  25. 2026-06-06 13:45 UTCEPSS rescore
  26. 2026-06-06 13:45 UTCEPSS rescore
  27. 2026-06-05 22:45 UTCEPSS rescore
  28. 2026-06-05 22:44 UTCEPSS rescore
  29. 2026-06-05 06:08 UTCEPSS rescore
  30. 2026-06-05 06:08 UTCEPSS rescore
  31. 2026-06-04 13:10 UTCEPSS rescore
  32. 2026-06-04 13:10 UTCEPSS rescore
  33. 2026-06-02 20:11 UTCEPSS rescore
  34. 2026-06-02 20:11 UTCEPSS rescore
  35. 2026-06-01 13:49 UTCEPSS rescore
  36. 2026-05-31 00:14 UTCEPSS rescore
  37. 2026-05-31 00:14 UTCEPSS rescore
  38. 2026-05-29 13:41 UTCEPSS rescore
  39. 2026-05-28 13:42 UTCEPSS rescore
  40. 2026-05-28 13:42 UTCEPSS rescore
  41. 2026-05-28 06:44 UTCEG score recompute
  42. 2026-05-28 06:44 UTCVendor advisory
  43. 2026-05-28 06:44 UTCGHSA enrichment
  44. 2026-05-27 13:38 UTCEPSS rescore
  45. 2026-05-27 13:38 UTCEPSS rescore
  46. 2026-05-26 13:42 UTCEPSS rescore
  47. 2026-05-26 13:42 UTCEPSS rescore
  48. 2026-05-26 07:17 UTCEPSS rescore
  49. 2026-05-26 07:17 UTCEPSS rescore
  50. 2026-05-26 04:46 UTCOSV refresh

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2018-12233?
CVE-2018-12233 is a high vulnerability published on June 12, 2018. In the eaget function in fs/jfs/xattr.c in the Linux kernel through 4.17.1, a memory corruption bug in JFS can be triggered by calling setxattr twice with two different extended attribute names on the same file. This vulnerability can be triggered by an unprivileged user with the ability to create…
When was CVE-2018-12233 disclosed?
CVE-2018-12233 was first published in the National Vulnerability Database on June 12, 2018, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2018-12233 actively exploited?
CVE-2018-12233 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 81.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2018-12233?
CVE-2018-12233 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2018-12233?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-12233, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2018-12233

Explore →

Is Your Infrastructure Affected by CVE-2018-12233?

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

Start Free Scan →Browse All CVEs