libbpf4.19 vulnerabilities (TuxCare)
325 vulnerabilities.
libbpf4.19TuxCareftrace: Fix possible use-after-free issue in ftrace_location()7.8 Highlibbpf4.19TuxCareRDMA/hns: Fix UAF for cq async event7.8 Highlibbpf4.19TuxCarestaging: rtl8712: fix use-after-free in rtl8712_dl_fw7.0 Highlibbpf4.19TuxCarecifs: Fix use-after-free in rdata->read_into_pages()9.8 Criticallibbpf4.19TuxCareRDMA/cma: Ensure rdma_addr_cancel() happens before issuing more requests7.8 Highlibbpf4.19TuxCareblk-cgroup: fix UAF by grabbing blkcg lock before destroying blkg pd7.8 Highlibbpf4.19TuxCarevirtio-net: Add validation for used length8.4 Highlibbpf4.19TuxCaredrm/vc4: don't check if plane->state->fb == state->fb7.8 Highlibbpf4.19TuxCaresmb: client: fix potential UAF in smb2_is_valid_lease_break()9.8 Criticallibbpf4.19TuxCareKVM: SVM: Flush pages under kvm->lock to fix UAF in svm_register_enc_region()7.8 Highlibbpf4.19TuxCareusb: gadget: f_ncm: Fix UAF ncm object at re-bind after usb ep transport error7.8 Highlibbpf4.19TuxCarecifs: fix underflow in parse_server_interfaces()9.4 Criticallibbpf4.19TuxCarescsi: scsi_debug: Fix out-of-bound read in resp_readcap16()7.1 Highlibbpf4.19TuxCareceph: prevent use-after-free in encode_cap_msg()8.8 Highlibbpf4.19TuxCareasix: fix uninit-value in asix_mdio_read()7.1 Highlibbpf4.19TuxCarewifi: iwlwifi: mvm: Fix a memory corruption issue7.8 Highlibbpf4.19TuxCareRDMA/srp: Do not call scsi_done() from srp_abort()9.8 Criticallibbpf4.19TuxCareDrivers: hv: vmbus: Use after free in __vmbus_open()8.4 Highlibbpf4.19TuxCarekyber: fix out of bounds access when preempted7.8 Highlibbpf4.19TuxCaresmb: client: fix potential OOBs in smb2_parse_contexts()8.1 Highlibbpf4.19TuxCareKernel: aoe: improper reference count leads to use-after-free vulnerability7.0 Highlibbpf4.19TuxCarebt_sock_recvmsg in net/bluetooth/af_bluetooth.c in the Linux kernel through 6.6.8 has a use-after...7.0 Highlibbpf4.19TuxCareThe Linux kernel NFSD implementation prior to versions 5.19.17 and 6.0.2 are vulnerable to buffer...7.5 Highlibbpf4.19TuxCareAn issue was discovered the x86 KVM subsystem in the Linux kernel before 5.18.17. Unprivileged...7.8 Highlibbpf4.19TuxCareThe overlayfs implementation in the linux kernel did not properly validate with respect to user...8.8 High