p PatchFirst

PatchFirst · Latest vulnerabilities

linux-oracle-7.0 vulnerabilities · Page 184

Vulnerabilities published for linux-oracle-7.0 in the last 30 days: 1031. Listed in the KEV catalogue: 0.

Filter vulnerabilities
Clear filters

Vulnerabilities: 6099

  1. CVE-2026-74306

    High · CVSS 7.8EPSS 0.13%Fix available

    vfio/qat: fix f_pos race in qat_vf_resume_write()

    In the Linux kernel, the following vulnerability has been resolved: vfio/qat: fix f_pos race in qat_vf_resume_write() qat_vf_resume_write() checks filp->f_pos before taking migf->lock, but copies into the migration-state buffer after taking the lock and re-reading the shared file position. Two concurrent writers could therefore pass the bounds check with the old offset, then have the second writer copy after the first advanced f_pos, writing past the end of the migration-state buffer. Take migf->lock before doing the boundary checks.

    • Update to 7.0.0-1013.13~24.04.1
    Published Updated
  2. CVE-2026-74305

    High · CVSS 7.8EPSS 0.18%Fix available

    bpf: Tighten cgroup storage cookie checks for prog arrays

    In the Linux kernel, the following vulnerability has been resolved: bpf: Tighten cgroup storage cookie checks for prog arrays The fix in commit abad3d0bad72 ("bpf: Fix oob access in cgroup local storage") is still incomplete. The prog-array compatibility check treats a program with no cgroup storage as compatible with any stored storage cookie. This allows a storage-less program to bridge a tail call chain between an entry program and a storage-using callee even though cgroup local storage at runtime still follows the caller's context, that is, A -> B(no storage) -> C(storage) path. Requiring exact cookie equality would break the legitimat

    • Update to 7.0.0-1013.13~24.04.1
    Published Updated
  3. CVE-2026-74304

    Not ratedEPSS 0.21%Fix available

    Bluetooth: hci_qca: fix NULL pointer dereference in qca_setup() for non-serdev device

    In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_qca: fix NULL pointer dereference in qca_setup() for non-serdev device hu->serdev is NULL for hci_uart attached via non-serdev paths, but qca_setup() unconditionally calls serdev_device_get_drvdata(hu->serdev) and dereferences the result, causing a NULL pointer dereference. Fix by guarding the dereference with a NULL check, consistent with the rest of qca_setup().

    • Update to 7.0.0-1013.13~24.04.1
    Published Updated
  4. CVE-2026-74303

    Not ratedEPSS 0.21%Fix available

    Bluetooth: hci_qca: fix NULL pointer dereference in qca_dmp_hdr() for non-serdev device

    In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_qca: fix NULL pointer dereference in qca_dmp_hdr() for non-serdev device hu->serdev is NULL for hci_uart attached via non-serdev paths, but qca_dmp_hdr() unconditionally dereferences hu->serdev->dev.driver->name, causing a NULL pointer dereference. Fix by guarding the dereference with a NULL check and falling back to "hci_ldisc_qca" for the non-serdev case.

    • Update to 7.0.0-1013.13~24.04.1
    Published Updated
  5. CVE-2026-74302

    High · CVSS 7.8EPSS 0.13%Fix available

    Bluetooth: hci_core: Fix UAF in hci_unregister_dev()

    In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_core: Fix UAF in hci_unregister_dev() hci_unregister_dev() does not disable cmd_timer and ncmd_timer before the hci_dev structure is freed. If a timeout fires during device teardown, the callback dereferences freed memory (including the hdev->reset function pointer), leading to a use-after-free. Add disable_delayed_work_sync() calls alongside the existing disable_work_sync() calls to ensure both timers are fully quiesced before teardown proceeds.

    • Update to 7.0.0-1013.13~24.04.1
    Published Updated
  6. CVE-2026-74301

    Not ratedEPSS 0.21%Fix available

    Bluetooth: btmtk: fix URB leak in alloc_mtk_intr_urb error path

    In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btmtk: fix URB leak in alloc_mtk_intr_urb error path When btmtk_isopkt_pad() fails, the previously allocated URB is not freed, leaking the urb structure. Add usb_free_urb() before returning the error.

    • Update to 7.0.0-1013.13~24.04.1
    Published Updated
  7. CVE-2026-74300

    High · CVSS 8.8EPSS 0.4%Fix available

    Bluetooth: hci: validate codec capability element length

    In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci: validate codec capability element length Read Local Codec Capabilities returns a sequence of capability elements. Each element starts with a one-byte length followed by that many payload bytes. hci_read_codec_capabilities() checks that the skb contains the length byte, but then validates only caps->len against the remaining skb length. A malformed controller response with one remaining byte and caps->len set to one passes that check even though the element needs two bytes. The parser then records a two-byte capability and copies one byte beyond the advert

    • Update to 7.0.0-1013.13~24.04.1
    Published Updated
  8. CVE-2026-74297

    High · CVSS 7.8EPSS 0.18%Fix available

    RDMA/mlx5: Fix undefined shift of user RQ WQE size

    In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Fix undefined shift of user RQ WQE size set_rq_size() computes the RQ WQE size as "1 << rq_wqe_shift" based on the user-provided rq_wqe_shift, which is only checked to be greater than 32, so shifts of 32 are still accepted. A shift of 31 also overflows a signed integer, leading to undefined behavior. Use check_shl_overflow() to compute the RQ WQE size and reject any invalid values.

    • Update to 7.0.0-1013.13~24.04.1
    Published Updated
  9. CVE-2026-74295

    High · CVSS 7.1EPSS 0.17%Fix available

    ASoC: codecs: hdac_hdmi: Validate written enum value

    In the Linux kernel, the following vulnerability has been resolved: ASoC: codecs: hdac_hdmi: Validate written enum value hdac_hdmi_set_pin_port_mux() uses the written enum value to index the texts array before calling snd_soc_dapm_put_enum_double(), which validates that the value is within the enum item range. An out-of-range value can therefore make the driver read past the texts array before the helper rejects the write. Move the lookup after the helper has accepted the value.

    • Update to 7.0.0-1013.13~24.04.1
    Published Updated
  10. CVE-2026-74294

    High · CVSS 7.3EPSS 0.13%Fix available

    ASoC: meson: aiu: Validate written enum values

    In the Linux kernel, the following vulnerability has been resolved: ASoC: meson: aiu: Validate written enum values The AIU HDMI and internal codec mux put callbacks use the written enum value with snd_soc_enum_item_to_val() before checking whether the value is valid for the enumeration. Reject out-of-range values before converting the enum item, matching the validation already done by the G12A HDMI and internal codec mux controls.

    • Update to 7.0.0-1013.13~24.04.1
    Published Updated
  11. CVE-2026-74293

    High · CVSS 7.8EPSS 0.18%Fix available

    ASoC: fsl: fsl_audmix: Validate written enum values

    In the Linux kernel, the following vulnerability has been resolved: ASoC: fsl: fsl_audmix: Validate written enum values fsl_audmix_put_mix_clk_src() and fsl_audmix_put_out_src() convert the user-provided enum item with snd_soc_enum_item_to_val() before checking whether the item is within the enum's item count. The generic snd_soc_put_enum_double() helper performs that validation, but these callbacks use the converted value first: the clock-source path tests it with BIT(), and the output-source path indexes the prms transition table with it. Reject out-of-range enum items before converting them.

    • Update to 7.0.0-1013.13~24.04.1
    Published Updated
  12. CVE-2026-74292

    High · CVSS 7.1EPSS 0.17%Fix available

    ASoC: tegra: tegra210_ahub: Validate written enum value

    In the Linux kernel, the following vulnerability has been resolved: ASoC: tegra: tegra210_ahub: Validate written enum value tegra_ahub_put_value_enum() reads e->values[item[0]] before checking whether item[0] is within the enum item range. The existing check therefore happens too late to prevent an out-of-range read of the values array. Move the check before the array access.

    • Update to 7.0.0-1013.13~24.04.1
    Published Updated
  13. CVE-2026-74291

    Not ratedEPSS 0.17%Fix available

    ASoC: topology: Check PCM and DAI name strings before use

    In the Linux kernel, the following vulnerability has been resolved: ASoC: topology: Check PCM and DAI name strings before use Topology objects store several PCM and DAI names in fixed-size UAPI arrays. Other topology parser paths validate these fields with bounded strnlen() checks before using them as C strings, but the PCM and DAI paths still pass some fixed-size arrays directly to strlen(), devm_kstrdup(), DAI lookup, and diagnostic prints. A malformed topology blob with a non-NUL-terminated PCM, DAI, or stream capability name can therefore make the parser read past the end of the fixed-size field. Reject unterminated PCM and DAI name f

    • Update to 7.0.0-1013.13~24.04.1
    Published Updated
  14. CVE-2026-74290

    Medium · CVSS 4.8EPSS 0.17%Fix available

    net/sched: cls_flow: Dont expose folded kernel pointers

    In the Linux kernel, the following vulnerability has been resolved: net/sched: cls_flow: Dont expose folded kernel pointers The flow classifier falls back to addr_fold() for fields that are missing from packet headers. In map mode, userspace controls mask, xor, rshift, addend and divisor, and can observe the resulting classid through class statistics. This allows a tc classifier in a user/network namespace to recover the 32-bit folded value of skb->sk, skb_dst() or skb_nfct(). Align with standard kernel practices for pointer hashing and replace the XOR folding with a keyed siphash (which is cryptographically secure)

    • Update to 7.0.0-1013.13~24.04.1
    Published Updated
  15. CVE-2026-74289

    High · CVSS 7.8EPSS 0.13%Fix available

    ipv4: fib: Don't dump dying fib_info in fib_leaf_notify().

    In the Linux kernel, the following vulnerability has been resolved: ipv4: fib: Don't dump dying fib_info in fib_leaf_notify(). syzbot reported use-after-free in nsim_fib4_prepare_event(). [0] The problem is that the following functions call fib_info_hold() / refcount_inc() while dumping fib_info under RCU, which is unsafe. * mlxsw_sp_router_fib4_event() * rocker_router_fib_event() * nsim_fib4_prepare_event() refcount_inc_not_zero() must be used, but it would be too late there. Let's guarantee the lifetime of fib_info in fib_leaf_notify(). Note that IPv6 does not need the corresponding change since fib6_table_dump() holds fib6_tab

    • Update to 7.0.0-1013.13~24.04.1
    Published Updated
  16. CVE-2026-74288

    High · CVSS 7.8EPSS 0.13%Fix available

    net: fib_rules: Don't dump dying fib_rule in fib_rules_dump().

    In the Linux kernel, the following vulnerability has been resolved: net: fib_rules: Don't dump dying fib_rule in fib_rules_dump(). rocker_router_fib_event() calls fib_rule_get() during RCU dump. If the fib_rule is dying, refcount_inc() will complain about it. Let's call refcount_inc_not_zero() in fib_rules_dump().

    • Update to 7.0.0-1013.13~24.04.1
    Published Updated
  17. CVE-2026-74287

    Critical · CVSS 9.1EPSS 0.73%Fix available

    sctp: validate embedded address parameter length

    In the Linux kernel, the following vulnerability has been resolved: sctp: validate embedded address parameter length sctp_verify_asconf() and sctp_verify_param() only validate ADD_IP, DEL_IP, and SET_PRIMARY parameters against a fixed minimum size of sizeof(struct sctp_addip_param) + sizeof(struct sctp_paramhdr). This ensures the outer parameter is large enough to contain an embedded address parameter header, but does not verify that the embedded address parameter's declared length fits within the bounds of the outer parameter. Later, sctp_process_param() and sctp_process_asconf_param() extract the embedded address parameter and pass it to

    • Update to 7.0.0-1012.12~24.04.1
    Published Updated
  18. CVE-2026-74286

    Not ratedEPSS 0.17%Fix available

    net: pfcp: allocate per-cpu tstats for PFCP netdevs

    In the Linux kernel, the following vulnerability has been resolved: net: pfcp: allocate per-cpu tstats for PFCP netdevs PFCP uses dev_get_tstats64() as its ndo_get_stats64 callback, but pfcp_link_setup() does not request NETDEV_PCPU_STAT_TSTATS. The net core therefore leaves dev->tstats NULL for PFCP devices. Creating a PFCP rtnetlink device can immediately ask the new netdev for stats while building the RTM_NEWLINK notification. That reaches dev_get_tstats64() and dereferences the NULL dev->tstats pointer. Set pcpu_stat_type to NETDEV_PCPU_STAT_TSTATS during PFCP link setup so the net core allocates the storage expected by dev_get_tsta

    • Update to 7.0.0-1013.13~24.04.1
    Published Updated
  19. CVE-2026-74284

    Not ratedEPSS 0.22%Fix available

    net/sched: sch_hfsc: Don't make class passive twice

    In the Linux kernel, the following vulnerability has been resolved: net/sched: sch_hfsc: Don't make class passive twice update_vf() is called from two places for the same class during a single dequeue when the class's child qdisc (e.g. codel/fq_codel) drops its last packets while dequeuing: 1. The child calls qdisc_tree_reduce_backlog(), which, now that the child is empty, invokes hfsc_qlen_notify() -> update_vf(cl, 0, 0) and turns the class passive (cl_nactive is decremented up the hierarchy). 2. hfsc_dequeue() then calls update_vf(cl, qdisc_pkt_len(skb), cur_time) to charge the dequeued bytes. On the second call the class is a

    • Update to 7.0.0-1013.13~24.04.1
    Published Updated

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →