rpm package
suse/kernel-source-rt&distro=SUSE Real Time Module 15 SP6
pkg:rpm/suse/kernel-source-rt&distro=SUSE%20Real%20Time%20Module%2015%20SP6
Vulnerabilities (3,740)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2025-38474 | Med | 5.5 | < 6.4.0-150600.10.49.1 | 6.4.0-150600.10.49.1 | Jul 28, 2025 | In the Linux kernel, the following vulnerability has been resolved: usb: net: sierra: check for no status endpoint The driver checks for having three endpoints and having bulk in and out endpoints, but not that the third endpoint is interrupt input. Rectify the omission. | |
| CVE-2025-38473 | Med | 5.5 | < 6.4.0-150600.10.49.1 | 6.4.0-150600.10.49.1 | Jul 28, 2025 | In the Linux kernel, the following vulnerability has been resolved: Bluetooth: Fix null-ptr-deref in l2cap_sock_resume_cb() syzbot reported null-ptr-deref in l2cap_sock_resume_cb(). [0] l2cap_sock_resume_cb() has a similar problem that was fixed by commit 1bff51ea59a9 ("Blueto | |
| CVE-2025-38472 | Cri | 9.8 | < 6.4.0-150600.10.52.1 | 6.4.0-150600.10.52.1 | Jul 28, 2025 | In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_conntrack: fix crash due to removal of uninitialised entry A crash in conntrack was reported while trying to unlink the conntrack entry from the hash bucket list: [exception RIP: __nf_ct_delet | |
| CVE-2025-38471 | Cri | 9.8 | < 6.4.0-150600.10.49.1 | 6.4.0-150600.10.49.1 | Jul 28, 2025 | In the Linux kernel, the following vulnerability has been resolved: tls: always refresh the queue when reading sock After recent changes in net-next TCP compacts skbs much more aggressively. This unearthed a bug in TLS where we may try to operate on an old skb when checking if | |
| CVE-2025-38470 | Hig | 7.8 | < 6.4.0-150600.10.49.1 | 6.4.0-150600.10.49.1 | Jul 28, 2025 | In the Linux kernel, the following vulnerability has been resolved: net: vlan: fix VLAN 0 refcount imbalance of toggling filtering during runtime Assuming the "rx-vlan-filter" feature is enabled on a net device, the 8021q module will automatically add or remove VLAN 0 when the | |
| CVE-2025-38468 | Med | 5.5 | < 6.4.0-150600.10.49.1 | 6.4.0-150600.10.49.1 | Jul 28, 2025 | In the Linux kernel, the following vulnerability has been resolved: net/sched: Return NULL when htb_lookup_leaf encounters an empty rbtree htb_lookup_leaf has a BUG_ON that can trigger with the following: tc qdisc del dev lo root tc qdisc add dev lo root handle 1: htb default | |
| CVE-2025-38467 | Med | 5.5 | < 6.4.0-150600.10.49.1 | 6.4.0-150600.10.49.1 | Jul 25, 2025 | In the Linux kernel, the following vulnerability has been resolved: drm/exynos: exynos7_drm_decon: add vblank check in IRQ handling If there's support for another console device (such as a TTY serial), the kernel occasionally panics during boot. The panic message and a relevant | |
| CVE-2025-38466 | Hig | 7.8 | < 6.4.0-150600.10.55.1 | 6.4.0-150600.10.55.1 | Jul 25, 2025 | In the Linux kernel, the following vulnerability has been resolved: perf: Revert to requiring CAP_SYS_ADMIN for uprobes Jann reports that uprobes can be used destructively when used in the middle of an instruction. The kernel only verifies there is a valid instruction at the re | |
| CVE-2025-38465 | Med | 5.5 | < 6.4.0-150600.10.49.1 | 6.4.0-150600.10.49.1 | Jul 25, 2025 | In the Linux kernel, the following vulnerability has been resolved: netlink: Fix wraparounds of sk->sk_rmem_alloc. Netlink has this pattern in some places if (atomic_read(&sk->sk_rmem_alloc) > sk->sk_rcvbuf) atomic_add(skb->truesize, &sk->sk_rmem_alloc); , which has the | |
| CVE-2025-38464 | Hig | 7.8 | < 6.4.0-150600.10.52.1 | 6.4.0-150600.10.52.1 | Jul 25, 2025 | In the Linux kernel, the following vulnerability has been resolved: tipc: Fix use-after-free in tipc_conn_close(). syzbot reported a null-ptr-deref in tipc_conn_close() during netns dismantle. [0] tipc_topsrv_stop() iterates tipc_net(net)->topsrv->conn_idr and calls tipc_conn_ | |
| CVE-2025-38463 | Hig | 7.8 | < 6.4.0-150600.10.49.1 | 6.4.0-150600.10.49.1 | Jul 25, 2025 | In the Linux kernel, the following vulnerability has been resolved: tcp: Correct signedness in skb remaining space calculation Syzkaller reported a bug [1] where sk->sk_forward_alloc can overflow. When we send data, if an skb exists at the tail of the write queue, the kernel w | |
| CVE-2025-38462 | Med | 4.7 | < 6.4.0-150600.10.49.1 | 6.4.0-150600.10.49.1 | Jul 25, 2025 | In the Linux kernel, the following vulnerability has been resolved: vsock: Fix transport_{g2h,h2g} TOCTOU vsock_find_cid() and vsock_dev_do_ioctl() may race with module unload. transport_{g2h,h2g} may become NULL after the NULL check. Introduce vsock_transport_local_cid() to p | |
| CVE-2025-38461 | Hig | 7.0 | < 6.4.0-150600.10.49.1 | 6.4.0-150600.10.49.1 | Jul 25, 2025 | In the Linux kernel, the following vulnerability has been resolved: vsock: Fix transport_* TOCTOU Transport assignment may race with module unload. Protect new_transport from becoming a stale pointer. This also takes care of an insecure call in vsock_use_local_transport(); add | |
| CVE-2025-38460 | Hig | 7.0 | < 6.4.0-150600.10.49.1 | 6.4.0-150600.10.49.1 | Jul 25, 2025 | In the Linux kernel, the following vulnerability has been resolved: atm: clip: Fix potential null-ptr-deref in to_atmarpd(). atmarpd is protected by RTNL since commit f3a0592b37b8 ("[ATM]: clip causes unregister hang"). However, it is not enough because to_atmarpd() is called | |
| CVE-2025-38459 | Hig | 7.8 | < 6.4.0-150600.10.52.1 | 6.4.0-150600.10.52.1 | Jul 25, 2025 | In the Linux kernel, the following vulnerability has been resolved: atm: clip: Fix infinite recursive call of clip_push(). syzbot reported the splat below. [0] This happens if we call ioctl(ATMARP_MKIP) more than once. During the first call, clip_mkip() sets clip_push() to vc | |
| CVE-2025-38458 | Med | 5.5 | < 6.4.0-150600.10.52.1 | 6.4.0-150600.10.52.1 | Jul 25, 2025 | In the Linux kernel, the following vulnerability has been resolved: atm: clip: Fix NULL pointer dereference in vcc_sendmsg() atmarpd_dev_ops does not implement the send method, which may cause crash as bellow. BUG: kernel NULL pointer dereference, address: 0000000000000000 PGD | |
| CVE-2025-38457 | Med | 5.5 | < 6.4.0-150600.10.49.1 | 6.4.0-150600.10.49.1 | Jul 25, 2025 | In the Linux kernel, the following vulnerability has been resolved: net/sched: Abort __tc_modify_qdisc if parent class does not exist Lion's patch [1] revealed an ancient bug in the qdisc API. Whenever a user creates/modifies a qdisc specifying as a parent another qdisc, the qd | |
| CVE-2025-38456 | Hig | 7.8 | < 6.4.0-150600.10.55.1 | 6.4.0-150600.10.55.1 | Jul 25, 2025 | In the Linux kernel, the following vulnerability has been resolved: ipmi:msghandler: Fix potential memory corruption in ipmi_create_user() The "intf" list iterator is an invalid pointer if the correct "intf->intf_num" is not found. Calling atomic_dec(&intf->nr_users) on and in | |
| CVE-2025-38455 | Hig | 7.8 | < 6.4.0-150600.10.49.1 | 6.4.0-150600.10.49.1 | Jul 25, 2025 | In the Linux kernel, the following vulnerability has been resolved: KVM: SVM: Reject SEV{-ES} intra host migration if vCPU creation is in-flight Reject migration of SEV{-ES} state if either the source or destination VM is actively creating a vCPU, i.e. if kvm_vm_ioctl_create_vc | |
| CVE-2025-38449 | Hig | 7.8 | < 6.4.0-150600.10.49.1 | 6.4.0-150600.10.49.1 | Jul 25, 2025 | In the Linux kernel, the following vulnerability has been resolved: drm/gem: Acquire references on GEM handles for framebuffers A GEM handle can be released while the GEM buffer object is attached to a DRM framebuffer. This leads to the release of the dma-buf backing the buffer |
- affected < 6.4.0-150600.10.49.1fixed 6.4.0-150600.10.49.1
In the Linux kernel, the following vulnerability has been resolved: usb: net: sierra: check for no status endpoint The driver checks for having three endpoints and having bulk in and out endpoints, but not that the third endpoint is interrupt input. Rectify the omission.
- affected < 6.4.0-150600.10.49.1fixed 6.4.0-150600.10.49.1
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: Fix null-ptr-deref in l2cap_sock_resume_cb() syzbot reported null-ptr-deref in l2cap_sock_resume_cb(). [0] l2cap_sock_resume_cb() has a similar problem that was fixed by commit 1bff51ea59a9 ("Blueto
- affected < 6.4.0-150600.10.52.1fixed 6.4.0-150600.10.52.1
In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_conntrack: fix crash due to removal of uninitialised entry A crash in conntrack was reported while trying to unlink the conntrack entry from the hash bucket list: [exception RIP: __nf_ct_delet
- affected < 6.4.0-150600.10.49.1fixed 6.4.0-150600.10.49.1
In the Linux kernel, the following vulnerability has been resolved: tls: always refresh the queue when reading sock After recent changes in net-next TCP compacts skbs much more aggressively. This unearthed a bug in TLS where we may try to operate on an old skb when checking if
- affected < 6.4.0-150600.10.49.1fixed 6.4.0-150600.10.49.1
In the Linux kernel, the following vulnerability has been resolved: net: vlan: fix VLAN 0 refcount imbalance of toggling filtering during runtime Assuming the "rx-vlan-filter" feature is enabled on a net device, the 8021q module will automatically add or remove VLAN 0 when the
- affected < 6.4.0-150600.10.49.1fixed 6.4.0-150600.10.49.1
In the Linux kernel, the following vulnerability has been resolved: net/sched: Return NULL when htb_lookup_leaf encounters an empty rbtree htb_lookup_leaf has a BUG_ON that can trigger with the following: tc qdisc del dev lo root tc qdisc add dev lo root handle 1: htb default
- affected < 6.4.0-150600.10.49.1fixed 6.4.0-150600.10.49.1
In the Linux kernel, the following vulnerability has been resolved: drm/exynos: exynos7_drm_decon: add vblank check in IRQ handling If there's support for another console device (such as a TTY serial), the kernel occasionally panics during boot. The panic message and a relevant
- affected < 6.4.0-150600.10.55.1fixed 6.4.0-150600.10.55.1
In the Linux kernel, the following vulnerability has been resolved: perf: Revert to requiring CAP_SYS_ADMIN for uprobes Jann reports that uprobes can be used destructively when used in the middle of an instruction. The kernel only verifies there is a valid instruction at the re
- affected < 6.4.0-150600.10.49.1fixed 6.4.0-150600.10.49.1
In the Linux kernel, the following vulnerability has been resolved: netlink: Fix wraparounds of sk->sk_rmem_alloc. Netlink has this pattern in some places if (atomic_read(&sk->sk_rmem_alloc) > sk->sk_rcvbuf) atomic_add(skb->truesize, &sk->sk_rmem_alloc); , which has the
- affected < 6.4.0-150600.10.52.1fixed 6.4.0-150600.10.52.1
In the Linux kernel, the following vulnerability has been resolved: tipc: Fix use-after-free in tipc_conn_close(). syzbot reported a null-ptr-deref in tipc_conn_close() during netns dismantle. [0] tipc_topsrv_stop() iterates tipc_net(net)->topsrv->conn_idr and calls tipc_conn_
- affected < 6.4.0-150600.10.49.1fixed 6.4.0-150600.10.49.1
In the Linux kernel, the following vulnerability has been resolved: tcp: Correct signedness in skb remaining space calculation Syzkaller reported a bug [1] where sk->sk_forward_alloc can overflow. When we send data, if an skb exists at the tail of the write queue, the kernel w
- affected < 6.4.0-150600.10.49.1fixed 6.4.0-150600.10.49.1
In the Linux kernel, the following vulnerability has been resolved: vsock: Fix transport_{g2h,h2g} TOCTOU vsock_find_cid() and vsock_dev_do_ioctl() may race with module unload. transport_{g2h,h2g} may become NULL after the NULL check. Introduce vsock_transport_local_cid() to p
- affected < 6.4.0-150600.10.49.1fixed 6.4.0-150600.10.49.1
In the Linux kernel, the following vulnerability has been resolved: vsock: Fix transport_* TOCTOU Transport assignment may race with module unload. Protect new_transport from becoming a stale pointer. This also takes care of an insecure call in vsock_use_local_transport(); add
- affected < 6.4.0-150600.10.49.1fixed 6.4.0-150600.10.49.1
In the Linux kernel, the following vulnerability has been resolved: atm: clip: Fix potential null-ptr-deref in to_atmarpd(). atmarpd is protected by RTNL since commit f3a0592b37b8 ("[ATM]: clip causes unregister hang"). However, it is not enough because to_atmarpd() is called
- affected < 6.4.0-150600.10.52.1fixed 6.4.0-150600.10.52.1
In the Linux kernel, the following vulnerability has been resolved: atm: clip: Fix infinite recursive call of clip_push(). syzbot reported the splat below. [0] This happens if we call ioctl(ATMARP_MKIP) more than once. During the first call, clip_mkip() sets clip_push() to vc
- affected < 6.4.0-150600.10.52.1fixed 6.4.0-150600.10.52.1
In the Linux kernel, the following vulnerability has been resolved: atm: clip: Fix NULL pointer dereference in vcc_sendmsg() atmarpd_dev_ops does not implement the send method, which may cause crash as bellow. BUG: kernel NULL pointer dereference, address: 0000000000000000 PGD
- affected < 6.4.0-150600.10.49.1fixed 6.4.0-150600.10.49.1
In the Linux kernel, the following vulnerability has been resolved: net/sched: Abort __tc_modify_qdisc if parent class does not exist Lion's patch [1] revealed an ancient bug in the qdisc API. Whenever a user creates/modifies a qdisc specifying as a parent another qdisc, the qd
- affected < 6.4.0-150600.10.55.1fixed 6.4.0-150600.10.55.1
In the Linux kernel, the following vulnerability has been resolved: ipmi:msghandler: Fix potential memory corruption in ipmi_create_user() The "intf" list iterator is an invalid pointer if the correct "intf->intf_num" is not found. Calling atomic_dec(&intf->nr_users) on and in
- affected < 6.4.0-150600.10.49.1fixed 6.4.0-150600.10.49.1
In the Linux kernel, the following vulnerability has been resolved: KVM: SVM: Reject SEV{-ES} intra host migration if vCPU creation is in-flight Reject migration of SEV{-ES} state if either the source or destination VM is actively creating a vCPU, i.e. if kvm_vm_ioctl_create_vc
- affected < 6.4.0-150600.10.49.1fixed 6.4.0-150600.10.49.1
In the Linux kernel, the following vulnerability has been resolved: drm/gem: Acquire references on GEM handles for framebuffers A GEM handle can be released while the GEM buffer object is attached to a DRM framebuffer. This leads to the release of the dma-buf backing the buffer
Page 34 of 187