LSN-0106-1: linux Ubuntu

Published
Published 20-08-2024Last modified 03-06-2026

Vulnerability summary

LSN-0106-1 is a vulnerability in linux Ubuntu with no CVSS score yet.

Priority
Insufficient evidence

No CVSS vector published; no exploitation reported by the 5 checked sources

Source freshness unavailable

How is this decided?
CVSS score
Not scored
010
No CVSS score recorded
EPSS scoreNot scoredRisk metrics not yet published.
KEVNot listedNot listed by any tracked catalog.
RansomwareNot flaggedNo ransomware use recorded.
Public exploits0No public exploits recorded

Advisory lineage

Upstream 3 · Downstream 0

Timeline

  1. 20-08-2024
    PublishedVulnerability first disclosed.
  2. 03-06-2026
    Last modifiedVulnerability information updated.

Description

Kernel Live Patch Security Notice In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: disallow timeout for anonymous sets Never used from userspace, disallow these parameters.(CVE-2023-52620) In the Linux kernel, the following vulnerability has been resolved: tls: fix race between tx work scheduling and socket close Similarly to previous commit, the submitting thread (recvmsg/sendmsg) may exit as soon as the async crypto handler calls complete(). Reorder scheduling the work before calling complete(). This seems more logical in the first place, as it's the inverse order of what the submitting thread will do.(CVE-2024-26585) 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.(CVE-2024-36016)

CVSS metrics

Risk metrics not yet published.

EPSS trend

No EPSS score has been published for this record yet.

Known exploited

Compare KEV catalogs
CISA KEV

Not in the CISA KEV catalog.

ENISA CNW

Not in the ENISA CNW catalog.

CIRCL

Not in the CIRCL catalog.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

No weakness data has been published for this record.

Affected systems

Version check

Known conditions: not stated in public data.

Ubuntu20 products
  • linux< 4.4.0-257.291 | < 4.15.0-227.239 | < 5.4.0-190.210 | < 5.15.0-117.127 | < 6.8.0-39.39
  • linux-aws< 4.4.0-1172.187 | < 4.15.0-1170.183 | < 5.4.0-1129.139 | < 5.15.0-1066.72 | < 6.8.0-1012.13
  • linux-aws-5.15< 5.15.0-1066.72~20.04.1
  • linux-aws-hwe< 4.15.0-1170.183~16.04.1
  • linux-azure< 4.15.0-1179.194~16.04.1 | < 5.4.0-1134.141 | < 5.15.0-1070.79 | < 6.8.0-1012.14

1 vendor · 20 products

References

4 links