Answer in brief
CVE-2024-36016 records a Unknown severity vulnerability in tty: n_gsm: fix possible out-of-bounds in gsm0_receive(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), linux/linux_kernel (generic), linux/linux_kernel (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2024-36016 records a Unknown severity vulnerability in tty: n_gsm: fix possible out-of-bounds in gsm0_receive(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), linux/linux_kernel (generic), linux/linux_kernel (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), linux/linux_kernel (generic), linux/linux_kernel (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=e1eaea46bb4020b38a141b84f88565d4603f8dd0 <9513d4148950b05bc99fa7314dc883cc0e1605e5 || >=e1eaea46bb4020b38a141b84f88565d4603f8dd0 <b229bc6c6ea9fe459fc3fa94fd0a27a2f32aca56 || >=e1eaea46bb4020b38a141b84f88565d4603f8dd0 <0fb736c9931e02dbc7d9a75044c8e1c039e50f04 || >=e1eaea46bb4020b38a141b84f88565d4603f8dd0 <4c267110fc110390704cc065edb9817fdd10ff54 || >=e1eaea46bb4020b38a141b84f88565d4603f8dd0 <46f52c89a7e7d2691b97a9728e4591d071ca8abc || >=e1eaea46bb4020b38a141b84f88565d4603f8dd0 <774d83b008eccb1c48c14dc5486e7aa255731350 || >=e1eaea46bb4020b38a141b84f88565d4603f8dd0 <f126ce7305fe88f49cdabc6db4168b9318898ea3 || >=e1eaea46bb4020b38a141b84f88565d4603f8dd0 <b890d45aaf02b564e6cae2d2a590f9649330857d || >=e1eaea46bb4020b38a141b84f88565d4603f8dd0 <47388e807f85948eefc403a8a5fdc5b406a65d5a | 9513d4148950b05bc99fa7314dc883cc0e1605e5, b229bc6c6ea9fe459fc3fa94fd0a27a2f32aca56, 0fb736c9931e02dbc7d9a75044c8e1c039e50f04, 4c267110fc110390704cc065edb9817fdd10ff54, 46f52c89a7e7d2691b97a9728e4591d071ca8abc, 774d83b008eccb1c48c14dc5486e7aa255731350, f126ce7305fe88f49cdabc6db4168b9318898ea3, b890d45aaf02b564e6cae2d2a590f9649330857d, 47388e807f85948eefc403a8a5fdc5b406a65d5a |
| Linux/Linuxgeneric | 2.6.35 | Not reported |
| linux/linux_kernelgeneric | >=e1eaea46bb40 <b890d45aaf02 | b890d45aaf02 |
| linux/linux_kernelgeneric | >=e1eaea46bb40 <47388e807f85 | 47388e807f85 |
| linux/linux_kernelgeneric | 2.6.35 | Not reported |
| linux/linux_kernelgeneric | >=e1eaea46bb40 <f126ce7305fe || >=e1eaea46bb40 <9513d4148950 || >=e1eaea46bb40 <b229bc6c6ea9 || >=e1eaea46bb40 <0fb736c9931e || >=e1eaea46bb40 <4c267110fc11 || e1eaea46bb40 || >=e1eaea46bb40 <774d83b008ec | f126ce7305fe, 9513d4148950, b229bc6c6ea9, 0fb736c9931e, 4c267110fc11, 774d83b008ec |
Published upstream
May 29, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), linux/linux_kernel (generic), linux/linux_kernel (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=e1eaea46bb4020b38a141b84f88565d4603f8dd0 <9513d4148950b05bc99fa7314dc883cc0e1605e5 || >=e1eaea46bb4020b38a141b84f88565d4603f8dd0 <b229bc6c6ea9fe459fc3fa94fd0a27a2f32aca56 || >=e1eaea46bb4020b38a141b84f88565d4603f8dd0 <0fb736c9931e02dbc7d9a75044c8e1c039e50f04 || >=e1eaea46bb4020b38a141b84f88565d4603f8dd0 <4c267110fc110390704cc065edb9817fdd10ff54 || >=e1eaea46bb4020b38a141b84f88565d4603f8dd0 <46f52c89a7e7d2691b97a9728e4591d071ca8abc || >=e1eaea46bb4020b38a141b84f88565d4603f8dd0 <774d83b008eccb1c48c14dc5486e7aa255731350 || >=e1eaea46bb4020b38a141b84f88565d4603f8dd0 <f126ce7305fe88f49cdabc6db4168b9318898ea3 || >=e1eaea46bb4020b38a141b84f88565d4603f8dd0 <b890d45aaf02b564e6cae2d2a590f9649330857d || >=e1eaea46bb4020b38a141b84f88565d4603f8dd0 <47388e807f85948eefc403a8a5fdc5b406a65d5a | 9513d4148950b05bc99fa7314dc883cc0e1605e5, b229bc6c6ea9fe459fc3fa94fd0a27a2f32aca56, 0fb736c9931e02dbc7d9a75044c8e1c039e50f04, 4c267110fc110390704cc065edb9817fdd10ff54, 46f52c89a7e7d2691b97a9728e4591d071ca8abc, 774d83b008eccb1c48c14dc5486e7aa255731350, f126ce7305fe88f49cdabc6db4168b9318898ea3, b890d45aaf02b564e6cae2d2a590f9649330857d, 47388e807f85948eefc403a8a5fdc5b406a65d5a |
| Linux/Linuxgeneric | 2.6.35 | Not reported |
| linux/linux_kernelgeneric | >=e1eaea46bb40 <b890d45aaf02 | b890d45aaf02 |
| linux/linux_kernelgeneric | >=e1eaea46bb40 <47388e807f85 | 47388e807f85 |
| linux/linux_kernelgeneric | 2.6.35 | Not reported |
| linux/linux_kernelgeneric | >=e1eaea46bb40 <f126ce7305fe || >=e1eaea46bb40 <9513d4148950 || >=e1eaea46bb40 <b229bc6c6ea9 || >=e1eaea46bb40 <0fb736c9931e || >=e1eaea46bb40 <4c267110fc11 || e1eaea46bb40 || >=e1eaea46bb40 <774d83b008ec | f126ce7305fe, 9513d4148950, b229bc6c6ea9, 0fb736c9931e, 4c267110fc11, 774d83b008ec |
Published upstream
May 29, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.