UBUNTU-CVE-2024-50076
In the Linux kernel, the following vulnerability has been resolved: vt: prevent kernel-infoleak in con_font_get() font.data may not initialize all memory spaces depending on the implementation of vc->vc_sw->con_font_get. This may cause info-leak, so to prevent this, it is safest to modify it to initialize the allocated memory space to 0, and it generally does not affect the overall performance of the system.
02 / AFFECTED SOFTWARE
Affected packages
14 explicit affected versions
29 explicit affected versions
10 explicit affected versions
11 explicit affected versions
1 explicit affected versions
6 explicit affected versions
2 explicit affected versions
13 explicit affected versions
7 explicit affected versions
26 explicit affected versions
37 explicit affected versions
17 explicit affected versions
10 explicit affected versions
10 explicit affected versions
10 explicit affected versions
13 explicit affected versions
13 explicit affected versions
1 explicit affected versions
37 explicit affected versions
8 explicit affected versions
4 explicit affected versions
14 explicit affected versions
8 explicit affected versions
19 explicit affected versions
18 explicit affected versions
23 explicit affected versions
7 explicit affected versions
10 explicit affected versions
33 explicit affected versions
11 explicit affected versions
16 explicit affected versions
13 explicit affected versions
12 explicit affected versions
38 explicit affected versions
1 explicit affected versions
51 explicit affected versions
13 explicit affected versions
16 explicit affected versions
10 explicit affected versions
10 explicit affected versions
13 explicit affected versions
11 explicit affected versions
1 explicit affected versions
1 explicit affected versions
10 explicit affected versions
1 explicit affected versions
20 explicit affected versions
8 explicit affected versions
17 explicit affected versions
1 explicit affected versions
13 explicit affected versions
21 explicit affected versions
6 explicit affected versions
13 explicit affected versions
12 explicit affected versions
7 explicit affected versions
14 explicit affected versions
18 explicit affected versions
12 explicit affected versions
26 explicit affected versions
1 explicit affected versions
23 explicit affected versions
7 explicit affected versions
14 explicit affected versions
22 explicit affected versions
5 explicit affected versions
14 explicit affected versions
19 explicit affected versions
3 explicit affected versions
23 explicit affected versions
23 explicit affected versions
26 explicit affected versions
12 explicit affected versions
13 explicit affected versions
15 explicit affected versions
44 explicit affected versions
4 explicit affected versions
4 explicit affected versions
16 explicit affected versions
9 explicit affected versions
12 explicit affected versions
7 explicit affected versions
13 explicit affected versions
14 explicit affected versions
7 explicit affected versions
19 explicit affected versions
13 explicit affected versions
7 explicit affected versions
10 explicit affected versions
14 explicit affected versions
18 explicit affected versions
3 explicit affected versions
16 explicit affected versions
43 explicit affected versions
24 explicit affected versions
20 explicit affected versions
19 explicit affected versions
11 explicit affected versions
12 explicit affected versions
35 explicit affected versions
12 explicit affected versions
13 explicit affected versions
6 explicit affected versions
12 explicit affected versions
1 explicit affected versions
50 explicit affected versions
11 explicit affected versions
12 explicit affected versions
27 explicit affected versions
12 explicit affected versions
7 explicit affected versions
03 / CONNECTIONS
Connected vulnerabilities
04 / EVIDENCE
Source records
In the Linux kernel, the following vulnerability has been resolved: vt: prevent kernel-infoleak in con_font_get() font.data may not initialize all memory spaces depending on the implementation of vc->vc_sw->con_font_get. This may cause info-leak, so to prevent this, it is safest to modify it to initialize the allocated memory space to 0, and it generally does not affect the overall performance of the system.
05 / REFERENCES
Further evidence
- https://git.kernel.org/linus/f956052e00de211b5c9ebaa1958366c23f82ee9e
- https://git.kernel.org/stable/c/adb1f312f38f0d2c928ceaff089262798cc260b4
- https://git.kernel.org/stable/c/dc2d5f02636c7587bdd6d1f60fc59c55860b00a4
- https://git.kernel.org/stable/c/f956052e00de211b5c9ebaa1958366c23f82ee9e
- https://ubuntu.com/security/CVE-2024-50076
- https://ubuntu.com/security/notices/USN-7276-1
- https://ubuntu.com/security/notices/USN-7277-1
- https://ubuntu.com/security/notices/USN-7310-1
- https://ubuntu.com/security/notices/USN-7383-1
- https://ubuntu.com/security/notices/USN-7383-2
- https://ubuntu.com/security/notices/USN-7384-1
- https://ubuntu.com/security/notices/USN-7384-2
- https://ubuntu.com/security/notices/USN-7385-1
- https://ubuntu.com/security/notices/USN-7386-1
- https://ubuntu.com/security/notices/USN-7403-1
- https://ubuntu.com/security/notices/USN-7451-1
- https://ubuntu.com/security/notices/USN-7468-1
- https://ubuntu.com/security/notices/USN-7523-1
- https://ubuntu.com/security/notices/USN-7524-1
- https://www.cve.org/CVERecord?id=CVE-2024-50076