CVEvulnerability

CVE-2024-36016

7.8 HIGH Published 2024-05-29 Modified 2026-08-04 Official page ↗
Status
Modified
Published
2024-05-29
Last modified
2026-08-04
Assigner
416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS 3.1 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)
7.8 HIGH — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS 3.1 (134c704f-9b21-4f2e-91b3-4a467353bcc0)
7.7 HIGH — CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
Weaknesses
CWE-125

Description

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.

Affected configurations

• linux linux kernel (>= 2.6.35 < 4.19.316) • linux linux kernel (>= 4.20 < 5.4.278) • linux linux kernel (>= 5.5 < 5.10.219) • linux linux kernel (>= 5.11 < 5.15.161) • linux linux kernel (>= 5.16 < 6.1.93) • linux linux kernel (>= 6.2 < 6.6.33) • linux linux kernel (>= 6.7 < 6.8.12) • linux linux kernel (>= 6.9 < 6.9.3)

Related

Weakness · CWE (1)

  • CWE-125 Out-of-bounds Read weakness

References