CVE-2024-36016

HIGHNVD 7.77.7—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.7 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 80% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this week
7.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.7Exploit: None knownExposed: 0

A fix is available — apply it.

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

tty: n_gsm: fix possible out-of-bounds in gsm0_receive()

Assuming the following:

  • side A configures the n_gsm in basic option mode
  • side B sends the header of a basic option mode frame with data length 1
  • side A switches to advanced option mode
  • side B sends 2 data bytes which exceeds gsm->len
Reason: gsm->len is not used in advanced option mode.
  • side A switches to basic option mode
  • side B keeps sending until gsm0_receive() writes past gsm->buf
Reason: Neither gsm->state nor gsm->len have been reset after reconfiguration.

Fix this by changing gsm->count to gsm->len comparison from equal to less than. Also add upper limit checks against the constant MAX_MRU in gsm0_receive() and gsm1_receive() to harden against memory corruption of gsm->len and gsm->mru.

All other checks remain as we still need to limit the data according to the user configuration and actual payload size.

CVSS v3
7.7
EG Score
7.7(medium)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

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
Severity77% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
18%
KEV
Not listed

Published

May 29, 2024

Last Modified

August 5, 2026

Advisory Details (9)

Auto-updated Aug 5, 2026
No patch confirmed yet.
generic

tty: n_gsm: fix possible out-of-bounds in gsm0_receive() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/47388e807f85948eefc403a8a5fdc5b406a65d5a
generic

tty: n_gsm: fix possible out-of-bounds in gsm0_receive() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b890d45aaf02b564e6cae2d2a590f9649330857d
generic
https://git.kernel.org/stable/c/f126ce7305fe88f49cdabc6db4168b9318898ea3
generic

tty: n_gsm: fix possible out-of-bounds in gsm0_receive() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/774d83b008eccb1c48c14dc5486e7aa255731350
generic

tty: n_gsm: fix possible out-of-bounds in gsm0_receive() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/46f52c89a7e7d2691b97a9728e4591d071ca8abc
generic

tty: n_gsm: fix possible out-of-bounds in gsm0_receive() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4c267110fc110390704cc065edb9817fdd10ff54
generic

tty: n_gsm: fix possible out-of-bounds in gsm0_receive() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0fb736c9931e02dbc7d9a75044c8e1c039e50f04
generic

tty: n_gsm: fix possible out-of-bounds in gsm0_receive() - kernel/git/stable/linux.git - Linux kernel stable tree

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

tty: n_gsm: fix possible out-of-bounds in gsm0_receive() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9513d4148950b05bc99fa7314dc883cc0e1605e5

Vendor Advisories for CVE-2024-36016(7)

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

Patch Availability(26)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-aws-lts-20.04 (5.4.0.1129.126) @ focal2026-05-24ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1059.57) @ jammy2026-05-24ubuntu
ubuntulinux-tools-azure (4.15.0.1179.194~14.04.1) @ trusty2026-05-24ubuntu
ubuntulinux-tools-oracle-edge (5.4.0.1129.138~18.04.1) @ bionic2026-05-24ubuntu
ubuntulowlatency-4.4 (4.4.0-168) @ trusty2026-05-24ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.117.117) @ jammy2026-05-24ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1070.68) @ jammy2026-05-24ubuntu
ubuntulinux-tools-oracle-64k (6.8.0-1010.10) @ noble2026-05-24ubuntu
ubuntulinux-tools-raspi-hwe-18.04-edge (5.4.0.1114.126~18.04.1) @ bionic2026-05-24ubuntu
ubuntulinux-tools-azure-edge (4.15.0.1179.194~16.04.1) @ xenial2026-05-24ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1065.71~20.04.1) @ focal2026-05-24ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1035.39) @ jammy2026-05-24ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.4.0-1048 (5.4.0-1048.52) @ focal2026-05-24ubuntu
ubuntulinux-virtual-hwe-16.04-edge (4.15.0.227.239~16.04.1) @ xenial2026-05-24ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.8.0-39.39) @ noble2026-05-24ubuntu
ubuntulinux-tools-lowlatency-hwe-22.04-edge (6.8.0-39.39.1) @ noble2026-05-24ubuntu
ubuntulinux-virtual-lts-xenial (4.4.0.257.263) @ xenial2026-05-24ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1065.73~20.04.1) @ focal2026-05-24ubuntu
redhatkernel-0:4.18.0-477.74.1.el8_82024-09-24redhat
redhatkernel-0:5.14.0-427.37.1.el9_42024-09-24redhat
redhatkernel-0:4.18.0-372.119.1.el8_62024-08-21redhat
redhatkernel-0:4.18.0-553.16.1.el8_102024-08-08redhat
redhatkernel-rt-0:4.18.0-553.16.1.rt7.357.el8_102024-08-08redhat
redhatkernel-rt-0:5.14.0-284.73.1.rt14.358.el9_22024-07-15redhat
redhatkernel-0:5.14.0-284.73.1.el9_22024-07-15redhat
linuxKernel @ 4.19.316—osv

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.

Additional Vendor Advisories

(18)

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 11× in last 7d / 47× 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 125 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-36016?
CVE-2024-36016 is a high vulnerability published on May 29, 2024. In the Linux kernel, the following vulnerability has been resolved: tty: ngsm: fix possible out-of-bounds in gsm0receive() Assuming the following: side A configures the n_gsm in basic option mode side B sends the header of a basic option mode frame with data length 1 side A switches to advanced…
When was CVE-2024-36016 disclosed?
CVE-2024-36016 was first published in the National Vulnerability Database on May 29, 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-2024-36016 actively exploited?
CVE-2024-36016 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 81.8% of all scored CVEs.
What is the CVSS score of CVE-2024-36016?
CVE-2024-36016 has a CVSS v3 base score of 7.7 (NVD).
How do I remediate CVE-2024-36016?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-36016, 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-2024-36016

Explore →

Is Your Infrastructure Affected by CVE-2024-36016?

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

Start Free Scan →Browse All CVEs