Republished vendor advisory. This ICSA is a verbatim republication of Siemens ProductCERT SSA-089022 from a direct conversion of the vendor's Common Security Advisory Framework (CSAF) advisory. This is republished to CISA's website as a means of increasing visibility and is provided "as-is" for informational purposes only. CISA is not responsible for the editorial or technical accuracy of republished advisories and provides no warranties of any kind regarding any information contained within this advisory. Further, CISA…
General Recommendations: As a general security measure, Siemens strongly recommends to protect network access to devices with appropriate mechanisms. In order to operate the devices in a protected IT environment, Siemens recommends to configure the environment according to Siemens' operational guidelines for Industrial Security (Download: https://www.siemens.com/cert/operational-guidelines-industrial-security), and to follow the recommendations in the product manuals. Additional information on Industrial Security by Siemens can be found at: https://www.siemens.com/industrialsecurity
Additional Resources: For further inquiries on security vulnerabilities in Siemens products and solutions, please contact the Siemens ProductCERT: https://www.siemens.com/cert/advisories
Credit: Siemens ProductCERT
From CISA's machine-readable CSAF 2.0 advisory (JSON).
| CVE | Weakness | CVSS v3 | Details |
|---|---|---|---|
| CVE-2025-32433 KEV | CWE-306 Missing Authentication for Critical Function | 10.0 Critical |
CVE-2025-32433 Erlang/OTP is a set of libraries for the Erlang programming language. Prior to versions OTP-27.3.3, OTP-26.2.5.11, and OTP-25.3.2.20, a SSH server may allow an attacker to perform unauthenticated remote code execution (RCE). By exploiting a flaw in SSH protocol message handling, a malicious actor could gain unauthorized access to affected systems and execute arbitrary commands without valid credentials. This issue is patched in versions OTP-27.3.3, OTP-26.2.5.11, and OTP-25.3.2.20. A temporary workaround involves disabling the SSH server or to prevent access via firewall rules. Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
| CVE-2024-52533 | CWE-787 Out-of-bounds Write | 9.8 Critical |
CVE-2024-52533 gio/gsocks4aproxy.c in GNOME GLib before 2.82.1 has an off-by-one error and resultant buffer overflow because SOCKS4_CONN_MSG_LEN is not sufficient for a trailing '\\0' character. Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
| CVE-2025-4517 | CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') | 9.4 Critical |
CVE-2025-4517 Allows arbitrary filesystem writes outside the extraction directory during extraction with filter="data". You are affected by this vulnerability if using the tarfile module to extract untrusted tar archives using TarFile.extractall() or TarFile.extract() using the filter= parameter with a value of "data" or "tar". See the tarfile extraction filters documentation https://docs.python.org/3/library/tarfile.html#tarfile-extraction-filter for more information. Note that for Python 3.14 or later the default value of filter= changed from "no filtering" to `"data", so if you are relying on this new default behavior then your usage is also affected. Note that none of these vulnerabilities significantly affect the installation of source distributions which are tar archives as source distributions already allow arbitrary code execution during the build process. However when evaluating source distributions it's important to avoid installing source distributions with suspicious links. Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
| CVE-2022-48174 | CWE-787 Out-of-bounds Write | 7.8 High |
CVE-2022-48174 There is a stack overflow vulnerability in ash.c:6030 in busybox before 1.35. In the environment of Internet of Vehicles, this vulnerability can be executed from command to arbitrary code execution. Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
| CVE-2023-42365 | CWE-416 Use After Free | 7.8 High |
CVE-2023-42365 A use-after-free vulnerability was discovered in BusyBox v.1.36.1 via a crafted awk pattern in the awk.c copyvar function. Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
| CVE-2025-39841 | CWE-20 Improper Input Validation | 7.8 High |
CVE-2025-39841 In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Fix buffer free/clear order in deferred receive path Fix a use-after-free window by correcting the buffer release sequence in the deferred receive path. The code freed the RQ buffer first and only then cleared the context pointer under the lock. Concurrent paths (e.g., ABTS and the repost path) also inspect and release the same pointer under the lock, so the old order could lead to double-free/UAF. Note that the repost path already uses the correct pattern: detach the pointer under the lock, then free it after dropping the lock. The deferred path should do the same. Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
| CVE-2025-39864 | CWE-20 Improper Input Validation | 7.8 High |
CVE-2025-39864 In the Linux kernel, the following vulnerability has been resolved: wifi: cfg80211: fix use-after-free in cmp_bss() Following bss_free() quirk introduced in commit 776b3580178f ("cfg80211: track hidden SSID networks properly"), adjust cfg80211_update_known_bss() to free the last beacon frame elements only if they're not shared via the corresponding 'hidden_beacon_bss' pointer. Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
| CVE-2024-41996 | CWE-295 Improper Certificate Validation | 7.5 High |
CVE-2024-41996 Validating the order of the public keys in the Diffie-Hellman Key Agreement Protocol, when an approved safe prime is used, allows remote attackers (from the client side) to trigger unnecessarily expensive server-side DHE modular-exponentiation calculations. The client may cause asymmetric resource consumption. The basic attack scenario is that the client must claim that it can only communicate with DHE, and the server must be configured to allow DHE and validate the order of the public key. Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
| CVE-2024-47619 | CWE-295 Improper Certificate Validation | 7.5 High |
CVE-2024-47619 syslog-ng is an enhanced log daemo. Prior to version 4.8.2, `tls_wildcard_match()` matches on certificates such as `foo.*.bar` although that is not allowed. It is also possible to pass partial wildcards such as `foo.a*c.bar` which glib matches but should be avoided / invalidated. This issue could have an impact on TLS connections, such as in man-in-the-middle situations. Version 4.8.2 contains a fix for the issue. Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
| CVE-2024-6197 | CWE-590 Free of Memory not on the Heap | 7.5 High |
CVE-2024-6197 libcurl's ASN1 parser has this utf8asn1str() function used for parsing an ASN.1 UTF-8 string. Itcan detect an invalid field and return error. Unfortunately, when doing so it also invokes `free()` on a 4 byte localstack buffer. Most modern malloc implementations detect this error and immediately abort. Some however accept the input pointer and add that memory to its list of available chunks. This leads to the overwriting of nearby stack memory. The content of the overwrite is decided by the `free()` implementation; likely to be memory pointers and a set of flags. The most likely outcome of exploting this flaw is a crash, although it cannot be ruled out that more serious results can be had in special circumstances. Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
| CVE-2025-4138 | CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') | 7.5 High |
CVE-2025-4138 Allows the extraction filter to be ignored, allowing symlink targets to point outside the destination directory, and the modification of some file metadata. You are affected by this vulnerability if using the tarfile module to extract untrusted tar archives using TarFile.extractall() or TarFile.extract() using the filter= parameter with a value of "data" or "tar". See the tarfile extraction filters documentation https://docs.python.org/3/library/tarfile.html#tarfile-extraction-filter for more information. Note that for Python 3.14 or later the default value of filter= changed from "no filtering" to `"data", so if you are relying on this new default behavior then your usage is also affected. Note that none of these vulnerabilities significantly affect the installation of source distributions which are tar archives as source distributions already allow arbitrary code execution during the build process. However when evaluating source distributions it's important to avoid installing source distributions with suspicious links. Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
| CVE-2025-4330 | CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') | 7.5 High |
CVE-2025-4330 Allows the extraction filter to be ignored, allowing symlink targets to point outside the destination directory, and the modification of some file metadata. You are affected by this vulnerability if using the tarfile module to extract untrusted tar archives using TarFile.extractall() or TarFile.extract() using the filter= parameter with a value of "data" or "tar". See the tarfile extraction filters documentation https://docs.python.org/3/library/tarfile.html#tarfile-extraction-filter for more information. Note that for Python 3.14 or later the default value of filter= changed from "no filtering" to `"data", so if you are relying on this new default behavior then your usage is also affected. Note that none of these vulnerabilities significantly affect the installation of source distributions which are tar archives as source distributions already allow arbitrary code execution during the build process. However when evaluating source distributions it's important to avoid installing source distributions with suspicious links. Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
| CVE-2025-4435 | CWE-682 Incorrect Calculation | 7.5 High |
CVE-2025-4435 When using a TarFile.errorlevel = 0 and extracting with a filter the documented behavior is that any filtered members would be skipped and not extracted. However the actual behavior of TarFile.errorlevel = 0 in affected versions is that the member would still be extracted and not skipped. Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
| CVE-2025-59375 | CWE-770 Allocation of Resources Without Limits or Throttling | 7.5 High |
CVE-2025-59375 libexpat in Expat before 2.7.2 allows attackers to trigger large dynamic memory allocations via a small document that is submitted for parsing. Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
| CVE-2025-9086 | CWE-125 Out-of-bounds Read | 7.5 High |
CVE-2025-9086 1. A cookie is set using the `secure` keyword for `https://target` 2. curl is redirected to or otherwise made to speak with `http://target` (same hostname, but using clear text HTTP) using the same cookie set 3. The same cookie name is set - but with just a slash as path (`path='/'`). Since this site is not secure, the cookie *should* just be ignored. 4. A bug in the path comparison logic makes curl read outside a heap buffer boundary The bug either causes a crash or it potentially makes the comparison come to the wrong conclusion and lets the clear-text site override the contents of the secure cookie, contrary to expectations and depending on the memory contents immediately following the single-byte allocation that holds the path. The presumed and correct behavior would be to plainly ignore the second set of the cookie since it was already set as secure on a secure host so overriding it on an insecure host should not be okay. Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
| CVE-2025-0665 | CWE-1341 Multiple Releases of Same Resource or Handle | 7.3 High |
CVE-2025-0665 libcurl would wrongly close the same eventfd file descriptor twice when taking down a connection channel after having completed a threaded name resolve. Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
| CVE-2025-0725 | CWE-680 Integer Overflow to Buffer Overflow | 7.3 High |
CVE-2025-0725 When libcurl is asked to perform automatic gzip decompression of content-encoded HTTP responses with the CURLOPT_ACCEPT_ENCODING option, using zlib 1.2.0.3 or older, an attacker-controlled integer overflow would make libcurl perform a buffer overflow. Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
| CVE-2025-38498 | CWE-20 Improper Input Validation | 7.3 High |
CVE-2025-38498 In the Linux kernel, the following vulnerability has been resolved: do_change_type(): refuse to operate on unmounted/not ours mounts Ensure that propagation settings can only be changed for mounts located in the caller's mount namespace. This change aligns permission checking with the rest of mount(2). Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
| CVE-2025-38350 | CWE-20 Improper Input Validation | 7.1 High |
CVE-2025-38350 In the Linux kernel, the following vulnerability has been resolved: net/sched: Always pass notifications when child class becomes empty Certain classful qdiscs may invoke their classes' dequeue handler on an enqueue operation. This may unexpectedly empty the child qdisc and thus make an in-flight class passive via qlen_notify(). Most qdiscs do not expect such behaviour at this point in time and may re-activate the class eventually anyways which will lead to a use-after-free. The referenced fix commit attempted to fix this behavior for the HFSC case by moving the backlog accounting around, though this turned out to be incomplete since the parent's parent may run into the issue too. The following reproducer demonstrates this use-after-free: tc qdisc add dev lo root handle 1: drr tc filter add dev lo parent 1: basic classid 1:1 tc class add dev lo parent 1: classid 1:1 drr tc qdisc add dev lo parent 1:1 handle 2: hfsc def 1 tc class add dev lo parent 2: classid 2:1 hfsc rt m1 8 d 1 m2 0 tc qdisc add dev lo parent 2:1 handle 3: netem tc qdisc add dev lo parent 3:1 handle 4: blackhole echo 1 | socat -u STDIN UDP4-DATAGRAM:127.0.0.1:8888 tc class delete dev lo classid 1:1 echo 1 | socat -u STDIN UDP4-DATAGRAM:127.0.0.1:8888 Since backlog accounting issues leading to a use-after-frees on stale class pointers is a recurring pattern at this point, this patch takes a different approach. Instead of trying to fix the accounting, the patch ensures that qdisc_tree_reduce_backlog always calls qlen_notify when the child qdisc is empty. This solves the problem because deletion of qdiscs always involves a call to qdisc_reset() and / or qdisc_purge_queue() which ultimately resets its qlen to 0 thus causing the following qdisc_tree_reduce_backlog() to report to the parent. Note that this may call qlen_notify on passive classes multiple times. This is not a problem after the recent patch series that made all the classful qdiscs qlen_notify() handlers idempotent. Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
| CVE-2025-39860 | CWE-20 Improper Input Validation | 7.1 High |
CVE-2025-39860 In the Linux kernel, the following vulnerability has been resolved: Bluetooth: Fix use-after-free in l2cap_sock_cleanup_listen() syzbot reported the splat below without a repro. In the splat, a single thread calling bt_accept_dequeue() freed sk and touched it after that. The root cause would be the racy l2cap_sock_cleanup_listen() call added by the cited commit. bt_accept_dequeue() is called under lock_sock() except for l2cap_sock_release(). Two threads could see the same socket during the list iteration in bt_accept_dequeue(): CPU1 CPU2 (close()) ---- ---- sock_hold(sk) sock_hold(sk); lock_sock(sk) <-- block close() sock_put(sk) bt_accept_unlink(sk) sock_put(sk) <-- refcnt by bt_accept_enqueue() release_sock(sk) lock_sock(sk) sock_put(sk) bt_accept_unlink(sk) sock_put(sk) <-- last refcnt bt_accept_unlink(sk) <-- UAF Depending on the timing, the other thread could show up in the "Freed by task" part. Let's call l2cap_sock_cleanup_listen() under lock_sock() in l2cap_sock_release(). [0]: BUG: KASAN: slab-use-after-free in debug_spin_lock_before kernel/locking/spinlock_debug.c:86 [inline] BUG: KASAN: slab-use-after-free in do_raw_spin_lock+0x26f/0x2b0 kernel/locking/spinlock_debug.c:115 Read of size 4 at addr ffff88803b7eb1c4 by task syz.5.3276/16995 CPU: 3 UID: 0 PID: 16995 Comm: syz.5.3276 Not tainted syzkaller #0 PREEMPT(full) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 Call Trace: <TASK> __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0xcd/0x630 mm/kasan/report.c:482 kasan_report+0xe0/0x110 mm/kasan/report.c:595 debug_spin_lock_before kernel/locking/spinlock_debug.c:86 [inline] do_raw_spin_lock+0x26f/0x2b0 kernel/locking/spinlock_debug.c:115 spin_lock_bh include/linux/spinlock.h:356 [inline] release_sock+0x21/0x220 net/core/sock.c:3746 bt_accept_dequeue+0x505/0x600 net/bluetooth/af_bluetooth.c:312 l2cap_sock_cleanup_listen+0x5c/0x2a0 net/bluetooth/l2cap_sock.c:1451 l2cap_sock_release+0x5c/0x210 net/bluetooth/l2cap_sock.c:1425 __sock_release+0xb3/0x270 net/socket.c:649 sock_close+0x1c/0x30 net/socket.c:1439 __fput+0x3ff/0xb70 fs/file_table.c:468 task_work_run+0x14d/0x240 kernel/task_work.c:227 resume_user_mode_work include/linux/resume_user_mode.h:50 [inline] exit_to_user_mode_loop+0xeb/0x110 kernel/entry/common.c:43 exit_to_user_mode_prepare include/linux/irq-entry-common.h:225 [inline] syscall_exit_to_user_mode_work include/linux/entry-common.h:175 [inline] syscall_exit_to_user_mode include/linux/entry-common.h:210 [inline] do_syscall_64+0x3f6/0x4c0 arch/x86/entry/syscall_64.c:100 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f2accf8ebe9 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ffdb6cb1378 EFLAGS: 00000246 ORIG_RAX: 00000000000001b4 RAX: 0000000000000000 RBX: 00000000000426fb RCX: 00007f2accf8ebe9 RDX: 0000000000000000 RSI: 000000000000001e RDI: 0000000000000003 RBP: 00007f2acd1b7da0 R08: 0000000000000001 R09: 00000012b6cb166f R10: 0000001b30e20000 R11: 0000000000000246 R12: 00007f2acd1b609c R13: 00007f2acd1b6090 R14: ffffffffffffffff R15: 00007ffdb6cb1490 </TASK> Allocated by task 5326: kasan_save_stack+0x33/0x60 mm/kasan/common.c:47 kasan_save_track+0x14/0x30 mm/kasan/common.c:68 poison_kmalloc_redzone mm/kasan/common.c:388 [inline] __kasan_kmalloc+0xaa/0xb0 mm/kasan/common.c:405 kasan_kmalloc include/linux/kasan.h:260 [inline] __do_kmalloc_node mm/slub.c:4365 [inline] __kmalloc_nopro ---truncated--- Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
| CVE-2025-38084 | CWE-20 Improper Input Validation | 7.0 High |
CVE-2025-38084 In the Linux kernel, the following vulnerability has been resolved: mm/hugetlb: unshare page tables during VMA split, not before Currently, __split_vma() triggers hugetlb page table unsharing through vm_ops->may_split(). This happens before the VMA lock and rmap locks are taken - which is too early, it allows racing VMA-locked page faults in our process and racing rmap walks from other processes to cause page tables to be shared again before we actually perform the split. Fix it by explicitly calling into the hugetlb unshare logic from __split_vma() in the same place where THP splitting also happens. At that point, both the VMA and the rmap(s) are write-locked. An annoying detail is that we can now call into the helper hugetlb_unshare_pmds() from two different locking contexts: 1. from hugetlb_split(), holding: - mmap lock (exclusively) - VMA lock - file rmap lock (exclusively) 2. hugetlb_unshare_all_pmds(), which I think is designed to be able to call us with only the mmap lock held (in shared mode), but currently only runs while holding mmap lock (exclusively) and VMA lock Backporting note: This commit fixes a racy protection that was introduced in commit b30c14cd6102 ("hugetlb: unshare some PMDs when splitting VMAs"); that commit claimed to fix an issue introduced in 5.13, but it should actually also go all the way back. [[email protected]: v2] Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
| CVE-2025-38086 | CWE-20 Improper Input Validation | 7.0 High |
CVE-2025-38086 In the Linux kernel, the following vulnerability has been resolved: net: ch9200: fix uninitialised access during mii_nway_restart In mii_nway_restart() the code attempts to call mii->mdio_read which is ch9200_mdio_read(). ch9200_mdio_read() utilises a local buffer called "buff", which is initialised with control_read(). However "buff" is conditionally initialised inside control_read(): if (err == size) { memcpy(data, buf, size); } If the condition of "err == size" is not met, then "buff" remains uninitialised. Once this happens the uninitialised "buff" is accessed and returned during ch9200_mdio_read(): return (buff[0] | buff[1] << 8); The problem stems from the fact that ch9200_mdio_read() ignores the return value of control_read(), leading to uinit-access of "buff". To fix this we should check the return value of control_read() and return early on error. Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
| CVE-2025-39865 | CWE-20 Improper Input Validation | 7.0 High |
CVE-2025-39865 In the Linux kernel, the following vulnerability has been resolved: tee: fix NULL pointer dereference in tee_shm_put tee_shm_put have NULL pointer dereference: __optee_disable_shm_cache --> shm = reg_pair_to_ptr(...);//shm maybe return NULL tee_shm_free(shm); --> tee_shm_put(shm);//crash Add check in tee_shm_put to fix it. panic log: Unable to handle kernel paging request at virtual address 0000000000100cca Mem abort info: ESR = 0x0000000096000004 EC = 0x25: DABT (current EL), IL = 32 bits SET = 0, FnV = 0 EA = 0, S1PTW = 0 FSC = 0x04: level 0 translation fault Data abort info: ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000 CM = 0, WnR = 0, TnD = 0, TagAccess = 0 GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 user pgtable: 4k pages, 48-bit VAs, pgdp=0000002049d07000 [0000000000100cca] pgd=0000000000000000, p4d=0000000000000000 Internal error: Oops: 0000000096000004 [#1] SMP CPU: 2 PID: 14442 Comm: systemd-sleep Tainted: P OE ------- ---- 6.6.0-39-generic #38 Source Version: 938b255f6cb8817c95b0dd5c8c2944acfce94b07 Hardware name: greatwall GW-001Y1A-FTH, BIOS Great Wall BIOS V3.0 10/26/2022 pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : tee_shm_put+0x24/0x188 lr : tee_shm_free+0x14/0x28 sp : ffff001f98f9faf0 x29: ffff001f98f9faf0 x28: ffff0020df543cc0 x27: 0000000000000000 x26: ffff001f811344a0 x25: ffff8000818dac00 x24: ffff800082d8d048 x23: ffff001f850fcd18 x22: 0000000000000001 x21: ffff001f98f9fb88 x20: ffff001f83e76218 x19: ffff001f83e761e0 x18: 000000000000ffff x17: 303a30303a303030 x16: 0000000000000000 x15: 0000000000000003 x14: 0000000000000001 x13: 0000000000000000 x12: 0101010101010101 x11: 0000000000000001 x10: 0000000000000001 x9 : ffff800080e08d0c x8 : ffff001f98f9fb88 x7 : 0000000000000000 x6 : 0000000000000000 x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000000 x2 : ffff001f83e761e0 x1 : 00000000ffff001f x0 : 0000000000100cca Call trace: tee_shm_put+0x24/0x188 tee_shm_free+0x14/0x28 __optee_disable_shm_cache+0xa8/0x108 optee_shutdown+0x28/0x38 platform_shutdown+0x28/0x40 device_shutdown+0x144/0x2b0 kernel_power_off+0x3c/0x80 hibernate+0x35c/0x388 state_store+0x64/0x80 kobj_attr_store+0x14/0x28 sysfs_kf_write+0x48/0x60 kernfs_fop_write_iter+0x128/0x1c0 vfs_write+0x270/0x370 ksys_write+0x6c/0x100 __arm64_sys_write+0x20/0x30 invoke_syscall+0x4c/0x120 el0_svc_common.constprop.0+0x44/0xf0 do_el0_svc+0x24/0x38 el0_svc+0x24/0x88 el0t_64_sync_handler+0x134/0x150 el0t_64_sync+0x14c/0x15 Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
| CVE-2024-8096 | CWE-295 Improper Certificate Validation | 6.5 Medium |
CVE-2024-8096 When curl is told to use the Certificate Status Request TLS extension, often referred to as OCSP stapling, to verify that the server certificate is valid, it might fail to detect some OCSP problems and instead wrongly consider the response as fine. If the returned status reports another error than 'revoked' (like for example 'unauthorized') it is not treated as a bad certficate. Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
| CVE-2024-9681 | CWE-697 Incorrect Comparison | 6.5 Medium |
CVE-2024-9681 When curl is asked to use HSTS, the expiry time for a subdomain might overwrite a parent domain's cache entry, making it end sooner or later than otherwise intended. This affects curl using applications that enable HSTS and use URLs with the insecure `HTTP://` scheme and perform transfers with hosts like `x.example.com` as well as `example.com` where the first host is a subdomain of the second host. (The HSTS cache either needs to have been populated manually or there needs to have been previous HTTPS accesses done as the cache needs to have entries for the domains involved to trigger this problem.) When `x.example.com` responds with `Strict-Transport-Security:` headers, this bug can make the subdomain's expiry timeout *bleed over* and get set for the parent domain `example.com` in curl's HSTS cache. The result of a triggered bug is that HTTP accesses to `example.com` get converted to HTTPS for a different period of time than what was asked for by the origin server. If `example.com` for example stops supporting HTTPS at its expiry time, curl might then fail to access `http://example.com` until the (wrongly set) timeout expires. This bug can also expire the parent's entry *earlier*, thus making curl inadvertently switch back to insecure HTTP earlier than otherwise intended. Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
| CVE-2025-9231 | CWE-385 Covert Timing Channel | 6.5 Medium |
CVE-2025-9231 Issue summary: A timing side-channel which could potentially allow remote recovery of the private key exists in the SM2 algorithm implementation on 64 bit ARM platforms. Impact summary: A timing side-channel in SM2 signature computations on 64 bit ARM platforms could allow recovering the private key by an attacker.. While remote key recovery over a network was not attempted by the reporter, timing measurements revealed a timing signal which may allow such an attack. OpenSSL does not directly support certificates with SM2 keys in TLS, and so this CVE is not relevant in most TLS contexts. However, given that it is possible to add support for such certificates via a custom provider, coupled with the fact that in such a custom provider context the private key may be recoverable via remote timing measurements, we consider this to be a Moderate severity issue. The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue, as SM2 is not an approved algorithm. Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
| CVE-2023-39810 | CWE-20 Improper Input Validation | 6.1 Medium |
CVE-2023-39810 An issue in the CPIO command of Busybox v1.33.2 allows attackers to execute a directory traversal. Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
| CVE-2025-1390 | CWE-284 Improper Access Control | 6.1 Medium |
CVE-2025-1390 The PAM module pam_cap.so of libcap configuration supports group names starting with “@”, during actual parsing, configurations not starting with “@” are incorrectly recognized as group names. This may result in nonintended users being granted an inherited capability set, potentially leading to security risks. Attackers can exploit this vulnerability to achieve local privilege escalation on systems where /etc/security/capability.conf is used to configure user inherited privileges by constructing specific usernames. Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
| CVE-2025-9232 | CWE-125 Out-of-bounds Read | 5.9 Medium |
CVE-2025-9232 Issue summary: An application using the OpenSSL HTTP client API functions may trigger an out-of-bounds read if the 'no_proxy' environment variable is set and the host portion of the authority component of the HTTP URL is an IPv6 address. Impact summary: An out-of-bounds read can trigger a crash which leads to Denial of Service for an application. The OpenSSL HTTP client API functions can be used directly by applications but they are also used by the OCSP client functions and CMP (Certificate Management Protocol) client implementation in OpenSSL. However the URLs used by these implementations are unlikely to be controlled by an attacker. In this vulnerable code the out of bounds read can only trigger a crash. Furthermore the vulnerability requires an attacker-controlled URL to be passed from an application to the OpenSSL function and the user has to have a 'no_proxy' environment variable set. For the aforementioned reasons the issue was assessed as Low severity. The vulnerable code was introduced in the following patch releases: 3.0.16, 3.1.8, 3.2.4, 3.3.3, 3.4.0 and 3.5.0. The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue, as the HTTP client implementation is outside the OpenSSL FIPS module boundary. Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
| CVE-2025-9230 | CWE-787 Out-of-bounds Write | 5.6 Medium |
CVE-2025-9230 An application trying to decrypt CMS messages encrypted using password based encryption can trigger an out-of-bounds read and write. Impact summary: This out-of-bounds read may trigger a crash which leads to Denial of Service for an application. The out-of-bounds write can cause a memory corruption which can have various consequences including a Denial of Service or Execution of attacker-supplied code. Although the consequences of a successful exploit of this vulnerability could be severe, the probability that the attacker would be able to perform it is low. Besides, password based (PWRI) encryption support in CMS messages is very rarely used. For that reason the issue was assessed as Moderate severity according to our Security Policy. The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue, as the CMS implementation is outside the OpenSSL FIPS module boundary. Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
| CVE-2023-42363 | CWE-416 Use After Free | 5.5 Medium |
CVE-2023-42363 A use-after-free vulnerability was discovered in xasprintf function in xfuncs_printf.c:344 in BusyBox v.1.36.1. Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
| CVE-2023-42364 | CWE-416 Use After Free | 5.5 Medium |
CVE-2023-42364 A use-after-free vulnerability in BusyBox v.1.36.1 allows attackers to cause a denial of service via a crafted awk pattern in the awk.c evaluate function. Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
| CVE-2023-42366 | CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer | 5.5 Medium |
CVE-2023-42366 A heap-buffer-overflow was discovered in BusyBox v.1.36.1 in the next_token function at awk.c:1159. Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
| CVE-2025-38085 | CWE-20 Improper Input Validation | 5.5 Medium |
CVE-2025-38085 In the Linux kernel, the following vulnerability has been resolved: mm/hugetlb: fix huge_pmd_unshare() vs GUP-fast race huge_pmd_unshare() drops a reference on a page table that may have previously been shared across processes, potentially turning it into a normal page table used in another process in which unrelated VMAs can afterwards be installed. If this happens in the middle of a concurrent gup_fast(), gup_fast() could end up walking the page tables of another process. While I don't see any way in which that immediately leads to kernel memory corruption, it is really weird and unexpected. Fix it with an explicit broadcast IPI through tlb_remove_table_sync_one(), just like we do in khugepaged when removing page tables for a THP collapse. Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
| CVE-2025-38345 | CWE-20 Improper Input Validation | 5.5 Medium |
CVE-2025-38345 In the Linux kernel, the following vulnerability has been resolved: ACPICA: fix acpi operand cache leak in dswstate.c ACPICA commit 987a3b5cf7175916e2a4b6ea5b8e70f830dfe732 I found an ACPI cache leak in ACPI early termination and boot continuing case. When early termination occurs due to malicious ACPI table, Linux kernel terminates ACPI function and continues to boot process. While kernel terminates ACPI function, kmem_cache_destroy() reports Acpi-Operand cache leak. Boot log of ACPI operand cache leak is as follows: >[ 0.585957] ACPI: Added _OSI(Module Device) >[ 0.587218] ACPI: Added _OSI(Processor Device) >[ 0.588530] ACPI: Added _OSI(3.0 _SCP Extensions) >[ 0.589790] ACPI: Added _OSI(Processor Aggregator Device) >[ 0.591534] ACPI Error: Illegal I/O port address/length above 64K: C806E00000004002/0x2 (20170303/hwvalid-155) >[ 0.594351] ACPI Exception: AE_LIMIT, Unable to initialize fixed events (20170303/evevent-88) >[ 0.597858] ACPI: Unable to start the ACPI Interpreter >[ 0.599162] ACPI Error: Could not remove SCI handler (20170303/evmisc-281) >[ 0.601836] kmem_cache_destroy Acpi-Operand: Slab cache still has objects >[ 0.603556] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.12.0-rc5 #26 >[ 0.605159] Hardware name: innotek gmb_h virtual_box/virtual_box, BIOS virtual_box 12/01/2006 >[ 0.609177] Call Trace: >[ 0.610063] ? dump_stack+0x5c/0x81 >[ 0.611118] ? kmem_cache_destroy+0x1aa/0x1c0 >[ 0.612632] ? acpi_sleep_proc_init+0x27/0x27 >[ 0.613906] ? acpi_os_delete_cache+0xa/0x10 >[ 0.617986] ? acpi_ut_delete_caches+0x3f/0x7b >[ 0.619293] ? acpi_terminate+0xa/0x14 >[ 0.620394] ? acpi_init+0x2af/0x34f >[ 0.621616] ? __class_create+0x4c/0x80 >[ 0.623412] ? video_setup+0x7f/0x7f >[ 0.624585] ? acpi_sleep_proc_init+0x27/0x27 >[ 0.625861] ? do_one_initcall+0x4e/0x1a0 >[ 0.627513] ? kernel_init_freeable+0x19e/0x21f >[ 0.628972] ? rest_init+0x80/0x80 >[ 0.630043] ? kernel_init+0xa/0x100 >[ 0.631084] ? ret_from_fork+0x25/0x30 >[ 0.633343] vgaarb: loaded >[ 0.635036] EDAC MC: Ver: 3.0.0 >[ 0.638601] PCI: Probing PCI hardware >[ 0.639833] PCI host bridge to bus 0000:00 >[ 0.641031] pci_bus 0000:00: root bus resource [io 0x0000-0xffff] > ... Continue to boot and log is omitted ... I analyzed this memory leak in detail and found acpi_ds_obj_stack_pop_and_ delete() function miscalculated the top of the stack. acpi_ds_obj_stack_push() function uses walk_state->operand_index for start position of the top, but acpi_ds_obj_stack_pop_and_delete() function considers index 0 for it. Therefore, this causes acpi operand memory leak. This cache leak causes a security threat because an old kernel (<= 4.9) shows memory locations of kernel functions in stack dump. Some malicious users could use this information to neutralize kernel ASLR. I made a patch to fix ACPI operand cache leak. Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
| CVE-2025-39839 | CWE-20 Improper Input Validation | 5.5 Medium |
CVE-2025-39839 In the Linux kernel, the following vulnerability has been resolved: batman-adv: fix OOB read/write in network-coding decode batadv_nc_skb_decode_packet() trusts coded_len and checks only against skb->len. XOR starts at sizeof(struct batadv_unicast_packet), reducing payload headroom, and the source skb length is not verified, allowing an out-of-bounds read and a small out-of-bounds write. Validate that coded_len fits within the payload area of both destination and source sk_buffs before XORing. Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
| CVE-2025-39846 | CWE-20 Improper Input Validation | 5.5 Medium |
CVE-2025-39846 In the Linux kernel, the following vulnerability has been resolved: pcmcia: Fix a NULL pointer dereference in __iodyn_find_io_region() In __iodyn_find_io_region(), pcmcia_make_resource() is assigned to res and used in pci_bus_alloc_resource(). There is a dereference of res in pci_bus_alloc_resource(), which could lead to a NULL pointer dereference on failure of pcmcia_make_resource(). Fix this bug by adding a check of res. Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
| CVE-2025-39853 | CWE-20 Improper Input Validation | 5.5 Medium |
CVE-2025-39853 In the Linux kernel, the following vulnerability has been resolved: i40e: Fix potential invalid access when MAC list is empty list_first_entry() never returns NULL - if the list is empty, it still returns a pointer to an invalid object, leading to potential invalid memory access when dereferenced. Fix this by using list_first_entry_or_null instead of list_first_entry. Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
| CVE-2024-12718 | CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') | 5.3 Medium |
CVE-2024-12718 Allows modifying some file metadata (e.g. last modified) with filter="data" or file permissions (chmod) with filter="tar" of files outside the extraction directory. You are affected by this vulnerability if using the tarfile module to extract untrusted tar archives using TarFile.extractall() or TarFile.extract() using the filter= parameter with a value of "data" or "tar". See the tarfile extraction filters documentation https://docs.python.org/3/library/tarfile.html#tarfile-extraction-filter for more information. Only Python versions 3.12 or later are affected by these vulnerabilities, earlier versions don't include the extraction filter feature. Note that for Python 3.14 or later the default value of filter= changed from "no filtering" to `"data", so if you are relying on this new default behavior then your usage is also affected. Note that none of these vulnerabilities significantly affect the installation of source distributions which are tar archives as source distributions already allow arbitrary code execution during the build process. However when evaluating source distributions it's important to avoid installing source distributions with suspicious links. Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
| CVE-2025-10148 | CWE-340 Generation of Predictable Numbers or Identifiers | 5.3 Medium |
CVE-2025-10148 curl's websocket code did not update the 32 bit mask pattern for each new outgoing frame as the specification says. Instead it used a fixed mask that persisted and was used throughout the entire connection. A predictable mask pattern allows for a malicious server to induce traffic between the two communicating parties that could be interpreted by an involved proxy (configured or transparent) as genuine, real, HTTP traffic with content and thereby poison its cache. That cached poisoned content could then be served to all users of that proxy. Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
| CVE-2025-27587 | CWE-385 Covert Timing Channel | 5.3 Medium |
CVE-2025-27587 OpenSSL 3.0.0 through 3.3.2 on the PowerPC architecture is vulnerable to a Minerva attack, exploitable by measuring the time of signing of random messages using the EVP_DigestSign API, and then using the private key to extract the K value (nonce) from the signatures. Next, based on the bit size of the extracted nonce, one can compare the signing time of full-sized nonces to signatures that used smaller nonces, via statistical tests. There is a side-channel in the P-364 curve that allows private key extraction (also, there is a dependency between the bit size of K and the size of the side channel). NOTE: This CVE is disputed because the OpenSSL security policy explicitly notes that any side channels which require same physical system to be detected are outside of the threat model for the software. The timing signal is so small that it is infeasible to be detected without having the attacking process running on the same physical system. Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
| CVE-2025-4516 | CWE-416 Use After Free | 5.1 Medium |
CVE-2025-4516 There is an issue in CPython when using `bytes.decode("unicode_escape", error="ignore|replace")`. If you are not using the "unicode_escape" encoding or an error handler your usage is not affected. To work-around this issue you may stop using the error= handler and instead wrap the bytes.decode() call in a try-except catching the DecodeError. Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
| CVE-2025-4373 | CWE-124 Buffer Underwrite ('Buffer Underflow') | 4.8 Medium |
CVE-2025-4373 GLib is vulnerable to an integer overflow in the g_string_insert_unichar() function. When the position at which to insert the character is large, the position will overflow, leading to a buffer underwrite. Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
| CVE-2023-7256 | CWE-415 Double Free | 4.4 Medium |
CVE-2023-7256 In affected libpcap versions during the setup of a remote packet capture the internal function sock_initaddress() calls getaddrinfo() and possibly freeaddrinfo(), but does not clearly indicate to the caller function whether freeaddrinfo() still remains to be called after the function returns. This makes it possible in some scenarios that both the function and its caller call freeaddrinfo() for the same allocated memory block. A similar problem was reported in Apple libpcap, to which Apple assigned CVE-2023-40400. Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
| CVE-2024-8006 | CWE-476 NULL Pointer Dereference | 4.4 Medium |
CVE-2024-8006 Remote packet capture support is disabled by default in libpcap. When a user builds libpcap with remote packet capture support enabled, one of the functions that become available is pcap_findalldevs_ex(). One of the function arguments can be a filesystem path, which normally means a directory with input data files. When the specified path cannot be used as a directory, the function receives NULL from opendir(), but does not check the return value and passes the NULL value to readdir(), which causes a NULL pointer derefence. Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
| CVE-2024-11053 | CWE-200 Exposure of Sensitive Information to an Unauthorized Actor | 3.7 Low |
CVE-2024-11053 When asked to both use a `.netrc` file for credentials and to follow HTTP redirects, curl could leak the password used for the first host to the followed-to host under certain circumstances. This flaw only manifests itself if the netrc file has an entry that matches the redirect target hostname but the entry either omits just the password or omits both login and password. Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
| CVE-2024-7264 | CWE-125 Out-of-bounds Read | 3.7 Low |
CVE-2024-7264 libcurl's ASN1 parser code has the `GTime2str()` function, used for parsing an ASN.1 Generalized Time field. If given an syntactically incorrect field, the parser might end up using -1 for the length of the *time fraction*, leading to a `strlen()` getting performed on a pointer to a heap buffer area that is not (purposely) null terminated. This flaw most likely leads to a crash, but can also lead to heap contents getting returned to the application when [CURLINFO_CERTINFO](https://curl.se/libcurl/c/CURLINFO_CERTINFO.html) is used. Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
| CVE-2025-3360 | CWE-190 Integer Overflow or Wraparound | 3.7 Low |
CVE-2025-3360 An integer overflow and buffer under-read in GLib occur when parsing a long invalid ISO 8601 timestamp with the g_date_time_new_from_iso8601() function. Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
| CVE-2025-0167 | CWE-200 Exposure of Sensitive Information to an Unauthorized Actor | 3.4 Low |
CVE-2025-0167 When asked to use a .netrc file for credentials and to follow HTTP redirects, curl could leak the password used for the first host to the followed-to host under certain circumstances. This flaw only manifests itself if the netrc file has a default entry that omits both login and password. A rare circumstance. Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
| CVE-2025-6141 | CWE-121 Stack-based Buffer Overflow | 3.3 Low |
CVE-2025-6141 A vulnerability has been found in GNU ncurses up to 6.5-20250322 and classified as problematic. This vulnerability affects the function postprocess_termcap of the file tinfo/parse_entry.c. The manipulation leads to stack-based buffer overflow. The attack needs to be approached locally. Upgrading to version 6.5-20250329 is able to address this issue. It is recommended to upgrade the affected component. Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
| CVE-2024-6874 | CWE-126 Buffer Over-read | 3.1 Low |
CVE-2024-6874 libcurl's URL API function [curl_url_get()](https://curl.se/libcurl/c/curl_url_get.html) offers punycode conversions, to and from IDN. Asking to convert a name that is exactly 256 bytes, libcurl ends up reading outside of a stack based buffer when built to use the *macidn* IDN backend. The conversion function then fills up the provided buffer exactly - but does not null terminate the string. This flaw can lead to stack contents accidently getting returned as part of the converted string. Vendor fix: Update to V3.3 or later version ↗ Vendor fix: See Section Additional Information. Vendor fix: Update to V3.3 or later version Affected, fixed & timelineAffected:
|
Scores and weakness types are as CISA or the republishing vendor stated them in this advisory; the linked CVE pages carry the independently enriched CVSS and SSVC assessments.
No coverage found in monitored research blogs or news feeds.
| CVE | CVSS | Affected |
|---|---|---|
| CVE-2025-32433 | 10.0 Critical | Erlang Erlang/OTP Erlang Erlang/OTP SSH server contains a missing authentication for critical function vulnerability. This could allow an attacker to execute arbitrary… |
| CVE-2024-52533 | 9.8 Critical | n/a n/a gio/gsocks4aproxy.c in GNOME GLib before 2.82.1 has an off-by-one error and resultant buffer overflow because SOCKS4_CONN_MSG_LEN is not sufficient f… |
| CVE-2025-39841 | 9.8 Critical | Linux Linux In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Fix buffer free/clear order in deferred receive path Fix a use-afte… |
| CVE-2025-4517 | 9.4 Critical | Python Software Foundation CPython Allows arbitrary filesystem writes outside the extraction directory during extraction with filter="data". You are affected by this vulnerability if… |
| CVE-2025-39839 | 8.8 High | Linux Linux In the Linux kernel, the following vulnerability has been resolved: batman-adv: fix OOB read/write in network-coding decode batadv_nc_skb_decode_pa… |
| CVE-2025-39864 | 8.8 High | Linux Linux In the Linux kernel, the following vulnerability has been resolved: wifi: cfg80211: fix use-after-free in cmp_bss() Following bss_free() quirk intr… |
| CVE-2025-39860 | 8.0 High | Linux Linux In the Linux kernel, the following vulnerability has been resolved: Bluetooth: Fix use-after-free in l2cap_sock_cleanup_listen() syzbot reported th… |
| CVE-2025-38084 | 7.8 High | Linux Linux In the Linux kernel, the following vulnerability has been resolved: mm/hugetlb: unshare page tables during VMA split, not before Currently, __split… |
| CVE-2025-38085 | 7.8 High | Linux Linux In the Linux kernel, the following vulnerability has been resolved: mm/hugetlb: fix huge_pmd_unshare() vs GUP-fast race huge_pmd_unshare() drops a … |
| CVE-2025-38350 | 7.8 High | Linux Linux In the Linux kernel, the following vulnerability has been resolved: net/sched: Always pass notifications when child class becomes empty Certain cla… |
| CVE-2025-38498 | 7.8 High | Linux Linux In the Linux kernel, the following vulnerability has been resolved: do_change_type(): refuse to operate on unmounted/not ours mounts Ensure that pr… |
| CVE-2024-41996 | 7.5 High | n/a n/a Validating the order of the public keys in the Diffie-Hellman Key Agreement Protocol, when an approved safe prime is used, allows remote attackers (f… |
| CVE-2024-47619 | 7.5 High | syslog-ng syslog-ng syslog-ng is an enhanced log daemo. Prior to version 4.8.2, `tls_wildcard_match()` matches on certificates such as `foo.*.bar` although that is not a… |
| CVE-2024-6197 | 7.5 High | curl curl libcurl's ASN1 parser has this utf8asn1str() function used for parsing an ASN.1 UTF-8 string. Itcan detect an invalid field and return error. Unfortu… |
| CVE-2025-4138 | 7.5 High | Python Software Foundation CPython Allows the extraction filter to be ignored, allowing symlink targets to point outside the destination directory, and the modification of some file me… |
| CVE-2025-4330 | 7.5 High | Python Software Foundation CPython Allows the extraction filter to be ignored, allowing symlink targets to point outside the destination directory, and the modification of some file me… |
| CVE-2025-4435 | 7.5 High | Python Software Foundation CPython When using a TarFile.errorlevel = 0 and extracting with a filter the documented behavior is that any filtered members would be skipped and not extrac… |
| CVE-2025-59375 | 7.5 High | libexpat project libexpat libexpat in Expat before 2.7.2 allows attackers to trigger large dynamic memory allocations via a small document that is submitted for parsing. |
| CVE-2025-9086 | 7.5 High | curl curl 1. A cookie is set using the `secure` keyword for `https://target` 2. curl is redirected to or otherwise made to speak with `http://target` (same … |
| CVE-2025-9230 | 7.5 High | OpenSSL OpenSSL Issue summary: An application trying to decrypt CMS messages encrypted using password based encryption can trigger an out-of-bounds read and write. … |
| CVE-2025-0725 | 7.3 High | curl curl When libcurl is asked to perform automatic gzip decompression of content-encoded HTTP responses with the `CURLOPT_ACCEPT_ENCODING` option, **using zl… |
| CVE-2025-0665 | 7.0 High | curl curl libcurl would wrongly close the same eventfd file descriptor twice when taking down a connection channel after having completed a threaded name resol… |
| CVE-2024-8096 | 6.5 Medium | curl curl When curl is told to use the Certificate Status Request TLS extension, often referred to as OCSP stapling, to verify that the server certificate is v… |
| CVE-2025-9231 | 6.5 Medium | OpenSSL OpenSSL Issue summary: A timing side-channel which could potentially allow remote recovery of the private key exists in the SM2 algorithm implementation on 6… |
| CVE-2024-7264 | 6.3 Medium | curl curl libcurl's ASN1 parser code has the `GTime2str()` function, used for parsing an ASN.1 Generalized Time field. If given an syntactically incorrect fiel… |
| CVE-2025-1390 | 6.1 Medium | OpenAnolis Anolis OS The PAM module pam_cap.so of libcap configuration supports group names starting with “@”, during actual parsing, configurations not starting with “@”… |
| CVE-2024-9681 | 5.9 Medium | curl curl When curl is asked to use HSTS, the expiry time for a subdomain might overwrite a parent domain's cache entry, making it end sooner or later than oth… |
| CVE-2025-4516 | 5.9 Medium | Python Software Foundation CPython There is an issue in CPython when using `bytes.decode("unicode_escape", error="ignore|replace")`. If you are not using the "unicode_escape" encoding … |
| CVE-2025-9232 | 5.9 Medium | OpenSSL OpenSSL Issue summary: An application using the OpenSSL HTTP client API functions may trigger an out-of-bounds read if the 'no_proxy' environment variable is… |
| CVE-2023-42364 | 5.5 Medium | n/a n/a A use-after-free vulnerability in BusyBox v.1.36.1 allows attackers to cause a denial of service via a crafted awk pattern in the awk.c evaluate func… |
| CVE-2024-12718 | 5.3 Medium | Python Software Foundation CPython Allows modifying some file metadata (e.g. last modified) with filter="data" or file permissions (chmod) with filter="tar" of files outside the extrac… |
| CVE-2025-10148 | 5.3 Medium | curl curl curl's WebSocket code did not update the 32-bit mask pattern for each new outgoing frame as the specification says. Instead it used a fixed mask that… |
| CVE-2025-27587 | 5.3 Medium | n/a n/a OpenSSL 3.0.0 through 3.3.2 on the PowerPC architecture is vulnerable to a Minerva attack, exploitable by measuring the time of signing of random mes… |
| CVE-2025-4373 | 4.8 Medium | — A flaw was found in GLib, which is vulnerable to an integer overflow in the g_string_insert_unichar() function. When the position at which to insert … |
| CVE-2025-6141 | 4.8 Medium | GNU ncurses A vulnerability has been found in GNU ncurses up to 6.5-20250322 and classified as problematic. This vulnerability affects the function postprocess_t… |
| CVE-2023-7256 | 4.4 Medium | The Tcpdump Group libpcap In affected libpcap versions during the setup of a remote packet capture the internal function sock_initaddress() calls getaddrinfo() and possibly fr… |
| CVE-2024-8006 | 4.4 Medium | The Tcpdump Group libpcap Remote packet capture support is disabled by default in libpcap. When a user builds libpcap with remote packet capture support enabled, one of the f… |
| CVE-2025-3360 | 3.7 Low | — A flaw was found in GLib. An integer overflow and buffer under-read occur when parsing a long invalid ISO 8601 timestamp with the g_date_time_new_fro… |
| CVE-2024-11053 | 3.4 Low | curl curl When asked to both use a `.netrc` file for credentials and to follow HTTP redirects, curl could leak the password used for the first host to the foll… |
| CVE-2025-0167 | 3.4 Low | curl curl When asked to use a `.netrc` file for credentials **and** to follow HTTP redirects, curl could leak the password used for the first host to the follo… |
| CVE-2024-6874 | 3.1 Low | curl curl libcurl's URL API function [curl_url_get()](https://curl.se/libcurl/c/curl_url_get.html) offers punycode conversions, to and from IDN. Asking to conv… |
| CVE-2022-48174 | — | n/a n/a There is a stack overflow vulnerability in ash.c:6030 in busybox before 1.35. In the environment of Internet of Vehicles, this vulnerability can be e… |
| CVE-2023-39810 | — | n/a n/a An issue in the CPIO command of Busybox v1.33.2 allows attackers to execute a directory traversal. |
| CVE-2023-42363 | — | n/a n/a A use-after-free vulnerability was discovered in xasprintf function in xfuncs_printf.c:344 in BusyBox v.1.36.1. |
| CVE-2023-42365 | — | n/a n/a A use-after-free vulnerability was discovered in BusyBox v.1.36.1 via a crafted awk pattern in the awk.c copyvar function. |
| CVE-2023-42366 | — | n/a n/a A heap-buffer-overflow was discovered in BusyBox v.1.36.1 in the next_token function at awk.c:1159. |
| CVE-2025-38086 | — | Linux Linux In the Linux kernel, the following vulnerability has been resolved: net: ch9200: fix uninitialised access during mii_nway_restart In mii_nway_resta… |
| CVE-2025-38345 | — | Linux Linux In the Linux kernel, the following vulnerability has been resolved: ACPICA: fix acpi operand cache leak in dswstate.c ACPICA commit 987a3b5cf717591… |
| CVE-2025-39846 | — | Linux Linux In the Linux kernel, the following vulnerability has been resolved: pcmcia: Fix a NULL pointer dereference in __iodyn_find_io_region() In __iodyn_f… |
| CVE-2025-39853 | — | Linux Linux In the Linux kernel, the following vulnerability has been resolved: i40e: Fix potential invalid access when MAC list is empty list_first_entry() ne… |
| CVE-2025-39865 | — | Linux Linux In the Linux kernel, the following vulnerability has been resolved: tee: fix NULL pointer dereference in tee_shm_put tee_shm_put have NULL pointer … |
Named by the advisory itself. Each CVE links to its tracked detail page.
Each vendor links to its Known Exploited Vulnerabilities catalog page. Only vendors that appear in the KEV catalog are listed, either because the publication cites one of their KEV entries or because it names them directly.