CVSS: 7.8EPSS: 0%CPEs: 4EXPL: 0CVE-2025-21646 – afs: Fix the maximum cell name length
https://notcve.org/view.php?id=CVE-2025-21646
19 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: afs: Fix the maximum cell name length The kafs filesystem limits the maximum length of a cell to 256 bytes, but a problem occurs if someone actually does that: kafs tries to create a directory under /proc/net/afs/ with the name of the cell, but that fails with a warning: WARNING: CPU: 0 PID: 9 at fs/proc/generic.c:405 because procfs limits the maximum filename length to 255. However, the DNS limits the maximum lookup length and, by extensio... • https://git.kernel.org/stable/c/c3e9f888263bb4df11cbd623ceced02081cb2f9f •
CVSS: 6.3EPSS: 0%CPEs: 5EXPL: 0CVE-2025-21645 – platform/x86/amd/pmc: Only disable IRQ1 wakeup where i8042 actually enabled it
https://notcve.org/view.php?id=CVE-2025-21645
19 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: platform/x86/amd/pmc: Only disable IRQ1 wakeup where i8042 actually enabled it Wakeup for IRQ1 should be disabled only in cases where i8042 had actually enabled it, otherwise "wake_depth" for this IRQ will try to drop below zero and there will be an unpleasant WARN() logged: kernel: atkbd serio0: Disabling IRQ1 wakeup source to avoid platform firmware bug kernel: ------------[ cut here ]------------ kernel: Unbalanced IRQ 1 wake disable ker... • https://git.kernel.org/stable/c/8e60615e8932167057b363c11a7835da7f007106 •
CVSS: 5.5EPSS: 0%CPEs: 2EXPL: 0CVE-2025-21644 – drm/xe: Fix tlb invalidation when wedging
https://notcve.org/view.php?id=CVE-2025-21644
19 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: drm/xe: Fix tlb invalidation when wedging If GuC fails to load, the driver wedges, but in the process it tries to do stuff that may not be initialized yet. This moves the xe_gt_tlb_invalidation_init() to be done earlier: as its own doc says, it's a software-only initialization and should had been named with the _early() suffix. Move it to be called by xe_gt_init_early(), so the locks and seqno are initialized, avoiding a NULL ptr deref when... • https://git.kernel.org/stable/c/c9474b726b932b5d555effd9ed0ae19f4da2367c •
CVSS: 5.5EPSS: 0%CPEs: 2EXPL: 0CVE-2025-21643 – netfs: Fix kernel async DIO
https://notcve.org/view.php?id=CVE-2025-21643
19 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: netfs: Fix kernel async DIO Netfslib needs to be able to handle kernel-initiated asynchronous DIO that is supplied with a bio_vec[] array. Currently, because of the async flag, this gets passed to netfs_extract_user_iter() which throws a warning and fails because it only handles IOVEC and UBUF iterators. This can be triggered through a combination of cifs and a loopback blockdev with something like: mount //my/cifs/share /foo dd if=/dev/zer... • https://git.kernel.org/stable/c/153a9961b551101cd38e94e26cd92fbfd198b19b •
CVSS: 7.8EPSS: 0%CPEs: 4EXPL: 0CVE-2025-21642 – mptcp: sysctl: sched: avoid using current->nsproxy
https://notcve.org/view.php?id=CVE-2025-21642
19 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: mptcp: sysctl: sched: avoid using current->nsproxy Using the 'net' structure via 'current' is not recommended for different reasons. First, if the goal is to use it to read or write per-netns data, this is inconsistent with how the "generic" sysctl entries are doing: directly by only using pointers set to the table entry, e.g. table->data. Linked to that, the per-netns data should always be obtained from the table linked to the netns it had... • https://git.kernel.org/stable/c/daad878a509d69da1761106cb48c091dfe9d522d •
CVSS: 5.5EPSS: 0%CPEs: 2EXPL: 0CVE-2025-21641 – mptcp: sysctl: blackhole timeout: avoid using current->nsproxy
https://notcve.org/view.php?id=CVE-2025-21641
19 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: mptcp: sysctl: blackhole timeout: avoid using current->nsproxy As mentioned in the previous commit, using the 'net' structure via 'current' is not recommended for different reasons: - Inconsistency: getting info from the reader's/writer's netns vs only from the opener's netns. - current->nsproxy can be NULL in some cases, resulting in an 'Oops' (null-ptr-deref), e.g. when the current task is exiting, as spotted by syzbot [1] using acct(2). ... • https://git.kernel.org/stable/c/27069e7cb3d1cea9377069266acf19b9cc5ad0ae •
CVSS: 5.5EPSS: 0%CPEs: 4EXPL: 0CVE-2025-21640 – sctp: sysctl: cookie_hmac_alg: avoid using current->nsproxy
https://notcve.org/view.php?id=CVE-2025-21640
19 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: sctp: sysctl: cookie_hmac_alg: avoid using current->nsproxy As mentioned in a previous commit of this series, using the 'net' structure via 'current' is not recommended for different reasons: - Inconsistency: getting info from the reader's/writer's netns vs only from the opener's netns. - current->nsproxy can be NULL in some cases, resulting in an 'Oops' (null-ptr-deref), e.g. when the current task is exiting, as spotted by syzbot [1] using... • https://git.kernel.org/stable/c/3c68198e75111a905ac2412be12bf7b29099729b •
CVSS: 6.4EPSS: 0%CPEs: 4EXPL: 0CVE-2025-21639 – sctp: sysctl: rto_min/max: avoid using current->nsproxy
https://notcve.org/view.php?id=CVE-2025-21639
19 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: sctp: sysctl: rto_min/max: avoid using current->nsproxy As mentioned in a previous commit of this series, using the 'net' structure via 'current' is not recommended for different reasons: - Inconsistency: getting info from the reader's/writer's netns vs only from the opener's netns. - current->nsproxy can be NULL in some cases, resulting in an 'Oops' (null-ptr-deref), e.g. when the current task is exiting, as spotted by syzbot [1] using acc... • https://git.kernel.org/stable/c/4f3fdf3bc59cafd14c3bc2c2369efad34c7aa8b5 •
CVSS: 5.5EPSS: 0%CPEs: 7EXPL: 0CVE-2025-21638 – sctp: sysctl: auth_enable: avoid using current->nsproxy
https://notcve.org/view.php?id=CVE-2025-21638
19 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: sctp: sysctl: auth_enable: avoid using current->nsproxy As mentioned in a previous commit of this series, using the 'net' structure via 'current' is not recommended for different reasons: - Inconsistency: getting info from the reader's/writer's netns vs only from the opener's netns. - current->nsproxy can be NULL in some cases, resulting in an 'Oops' (null-ptr-deref), e.g. when the current task is exiting, as spotted by syzbot [1] using acc... • https://git.kernel.org/stable/c/b14878ccb7fac0242db82720b784ab62c467c0dc •
CVSS: 5.5EPSS: 0%CPEs: 4EXPL: 0CVE-2025-21637 – sctp: sysctl: udp_port: avoid using current->nsproxy
https://notcve.org/view.php?id=CVE-2025-21637
19 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: sctp: sysctl: udp_port: avoid using current->nsproxy As mentioned in a previous commit of this series, using the 'net' structure via 'current' is not recommended for different reasons: - Inconsistency: getting info from the reader's/writer's netns vs only from the opener's netns. - current->nsproxy can be NULL in some cases, resulting in an 'Oops' (null-ptr-deref), e.g. when the current task is exiting, as spotted by syzbot [1] using acct(2... • https://git.kernel.org/stable/c/046c052b475e7119b6a30e3483e2888fc606a2f8 •