In the Linux kernel, the following vulnerability has been resolved: net: bcmgenet: Use stronger register read/writes to assure ordering GCC12 appears to be much smarter about its dependency tracking and is aware that the relaxed variants are just normal loads and stores and this is causing problems like: [ 210.074549] ------------[ cut here ]------------ [ 210.079223] NETDEV WATCHDOG: enabcm6e4ei0 (bcmgenet): transmit queue 1 timed out [ 210.086717] WARNING: CPU: 1 PID: 0 at net/sched/sch_generic.c:529 dev_watchdog+0x234/0x240 [ 210.095044] Modules linked in: genet(E) nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat] [ 210.146561] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [ 210.146927] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G E 5.17.0-rc7G12+ #58 [ 210.153226] CPPC Cpufreq:cppc_scale_freq_workfn: failed to read perf counters [ 210.161349] Hardware name: Raspberry Pi Foundation Raspberry Pi 4 Model B/Raspberry Pi 4 Model B, BIOS EDK2-DEV 02/08/2022 [ 210.161353] pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 210.161358] pc : dev_watchdog+0x234/0x240 [ 210.161364] lr : dev_watchdog+0x234/0x240 [ 210.161368] sp : ffff8000080a3a40 [ 210.161370] x29: ffff8000080a3a40 x28: ffffcd425af87000 x27: ffff8000080a3b20 [ 210.205150] x26: ffffcd425aa00000 x25: 0000000000000001 x24: ffffcd425af8ec08 [ 210.212321] x23: 0000000000000100 x22: ffffcd425af87000 x21: ffff55b142688000 [ 210.219491] x20: 0000000000000001 x19: ffff55b1426884c8 x18: ffffffffffffffff [ 210.226661] x17: 64656d6974203120 x16: 0000000000000001 x15: 6d736e617274203a [ 210.233831] x14: 2974656e65676d63 x13: ffffcd4259c300d8 x12: ffffcd425b07d5f0 [ 210.241001] x11: 00000000ffffffff x10: ffffcd425b07d5f0 x9 : ffffcd4258bdad9c [ 210.248171] x8 : 00000000ffffdfff x7 : 000000000000003f x6 : 0000000000000000 [ 210.255341] x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000001000 [ 210.262511] x2 : 0000000000001000 x1 : 0000000000000005 x0 : 0000000000000044 [ 210.269682] Call trace: [ 210.272133] dev_watchdog+0x234/0x240 [ 210.275811] call_timer_fn+0x3c/0x15c [ 210.279489] __run_timers.part.0+0x288/0x310 [ 210.283777] run_timer_softirq+0x48/0x80 [ 210.287716] __do_softirq+0x128/0x360 [ 210.291392] __irq_exit_rcu+0x138/0x140 [ 210.295243] irq_exit_rcu+0x1c/0x30 [ 210.298745] el1_interrupt+0x38/0x54 [ 210.302334] el1h_64_irq_handler+0x18/0x24 [ 210.306445] el1h_64_irq+0x7c/0x80 [ 210.309857] arch_cpu_idle+0x18/0x2c [ 210.313445] default_idle_call+0x4c/0x140 [ 210.317470] cpuidle_idle_call+0x14c/0x1a0 [ 210.321584] do_idle+0xb0/0x100 [ 210.324737] cpu_startup_entry+0x30/0x8c [ 210.328675] secondary_start_kernel+0xe4/0x110 [ 210.333138] __secondary_switched+0x94/0x98 The assumption when these were relaxed seems to be that device memory would be mapped non reordering, and that other constructs (spinlocks/etc) would provide the barriers to assure that packet data and in memory rings/queues were ordered with respect to device register reads/writes. This itself seems a bit sketchy, but the real problem with GCC12 is that it is moving the actual reads/writes around at will as though they were independent operations when in truth they are not, but the compiler can't know that. When looking at the assembly dumps for many of these routines its possible to see very clean, but not strictly in program order operations occurring as the compiler would be free to do if these weren't actually register reads/write operations. Its possible to suppress the timeout with a liberal bit of dma_mb()'s sprinkled around but the device still seems unable to reliably send/receive data. A better plan is to use the safer readl/writel everywhere. Since this partially reverts an older commit, which notes the use of the relaxed variants for performance reasons. I would suggest that any performance problems ---truncated---

The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2025-988688 advisory.

    In the Linux kernel, the following vulnerability has been resolved:

    net: bcmgenet: Use stronger register read/writes to assure ordering

    GCC12 appears to be much smarter about its dependency tracking and is     aware that the relaxed variants are just normal loads and stores and     this is causing problems like:

    [  210.074549] ------------[ cut here ]------------     [  210.079223] NETDEV WATCHDOG: enabcm6e4ei0 (bcmgenet): transmit queue 1 timed out     [  210.086717] WARNING: CPU: 1 PID: 0 at net/sched/sch_generic.c:529 dev_watchdog+0x234/0x240     [  210.095044] Modules linked in: genet(E) nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet     nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat]     [  210.146561] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110     [  210.146927] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G            E     5.17.0-rc7G12+ #58     [  210.153226] CPPC Cpufreq:cppc_scale_freq_workfn: failed to read perf counters     [  210.161349] Hardware name: Raspberry Pi Foundation Raspberry Pi 4 Model B/Raspberry Pi 4 Model B, BIOS     EDK2-DEV 02/08/2022     [  210.161353] pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)     [  210.161358] pc : dev_watchdog+0x234/0x240     [  210.161364] lr : dev_watchdog+0x234/0x240     [  210.161368] sp : ffff8000080a3a40     [  210.161370] x29: ffff8000080a3a40 x28: ffffcd425af87000 x27: ffff8000080a3b20     [  210.205150] x26: ffffcd425aa00000 x25: 0000000000000001 x24: ffffcd425af8ec08     [  210.212321] x23: 0000000000000100 x22: ffffcd425af87000 x21: ffff55b142688000     [  210.219491] x20: 0000000000000001 x19: ffff55b1426884c8 x18: ffffffffffffffff     [  210.226661] x17: 64656d6974203120 x16: 0000000000000001 x15: 6d736e617274203a     [  210.233831] x14: 2974656e65676d63 x13: ffffcd4259c300d8 x12: ffffcd425b07d5f0     [  210.241001] x11: 00000000ffffffff x10: ffffcd425b07d5f0 x9 : ffffcd4258bdad9c     [  210.248171] x8 : 00000000ffffdfff x7 : 000000000000003f x6 : 0000000000000000     [  210.255341] x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000001000     [  210.262511] x2 : 0000000000001000 x1 : 0000000000000005 x0 : 0000000000000044     [  210.269682] Call trace:
    [  210.272133]  dev_watchdog+0x234/0x240     [  210.275811]  call_timer_fn+0x3c/0x15c     [  210.279489]  __run_timers.part.0+0x288/0x310     [  210.283777]  run_timer_softirq+0x48/0x80     [  210.287716]  __do_softirq+0x128/0x360     [  210.291392]  __irq_exit_rcu+0x138/0x140     [  210.295243]  irq_exit_rcu+0x1c/0x30     [  210.298745]  el1_interrupt+0x38/0x54     [  210.302334]  el1h_64_irq_handler+0x18/0x24     [  210.306445]  el1h_64_irq+0x7c/0x80     [  210.309857]  arch_cpu_idle+0x18/0x2c     [  210.313445]  default_idle_call+0x4c/0x140     [  210.317470]  cpuidle_idle_call+0x14c/0x1a0     [  210.321584]  do_idle+0xb0/0x100     [  210.324737]  cpu_startup_entry+0x30/0x8c     [  210.328675]  secondary_start_kernel+0xe4/0x110     [  210.333138]  __secondary_switched+0x94/0x98

    The assumption when these were relaxed seems to be that device memory     would be mapped non reordering, and that other constructs     (spinlocks/etc) would provide the barriers to assure that packet data     and in memory rings/queues were ordered with respect to device     register reads/writes. This itself seems a bit sketchy, but the real     problem with GCC12 is that it is moving the actual reads/writes around     at will as though they were independent operations when in truth they     are not, but the compiler can't know that. When looking at the     assembly dumps for many of these routines its possible to see very     clean, but not strictly in program order operations occurring as the     compiler would be free to do if these weren't actually register     reads/write operations.

    Its possible to suppress the timeout with a liberal bit of dma_mb()'s     sprinkled around but the device still seems unable to reliably     send/receive data. A better plan is to use the safer readl/writel     everywhere.

    Since this partially reverts an older commit, which notes the use of     the relaxed variants for performance reasons. I would suggest that     any performance problems
    ---truncated---

Tenable has extracted the preceding description block directly from the Unity Linux security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2025-989592 advisory.

    In the Linux kernel, the following vulnerability has been resolved:

    net: bcmgenet: Use stronger register read/writes to assure ordering

    GCC12 appears to be much smarter about its dependency tracking and is     aware that the relaxed variants are just normal loads and stores and     this is causing problems like:

    [  210.074549] ------------[ cut here ]------------     [  210.079223] NETDEV WATCHDOG: enabcm6e4ei0 (bcmgenet): transmit queue 1 timed out     [  210.086717] WARNING: CPU: 1 PID: 0 at net/sched/sch_generic.c:529 dev_watchdog+0x234/0x240     [  210.095044] Modules linked in: genet(E) nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet     nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat]     [  210.146561] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110     [  210.146927] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G            E     5.17.0-rc7G12+ #58     [  210.153226] CPPC Cpufreq:cppc_scale_freq_workfn: failed to read perf counters     [  210.161349] Hardware name: Raspberry Pi Foundation Raspberry Pi 4 Model B/Raspberry Pi 4 Model B, BIOS     EDK2-DEV 02/08/2022     [  210.161353] pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)     [  210.161358] pc : dev_watchdog+0x234/0x240     [  210.161364] lr : dev_watchdog+0x234/0x240     [  210.161368] sp : ffff8000080a3a40     [  210.161370] x29: ffff8000080a3a40 x28: ffffcd425af87000 x27: ffff8000080a3b20     [  210.205150] x26: ffffcd425aa00000 x25: 0000000000000001 x24: ffffcd425af8ec08     [  210.212321] x23: 0000000000000100 x22: ffffcd425af87000 x21: ffff55b142688000     [  210.219491] x20: 0000000000000001 x19: ffff55b1426884c8 x18: ffffffffffffffff     [  210.226661] x17: 64656d6974203120 x16: 0000000000000001 x15: 6d736e617274203a     [  210.233831] x14: 2974656e65676d63 x13: ffffcd4259c300d8 x12: ffffcd425b07d5f0     [  210.241001] x11: 00000000ffffffff x10: ffffcd425b07d5f0 x9 : ffffcd4258bdad9c     [  210.248171] x8 : 00000000ffffdfff x7 : 000000000000003f x6 : 0000000000000000     [  210.255341] x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000001000     [  210.262511] x2 : 0000000000001000 x1 : 0000000000000005 x0 : 0000000000000044     [  210.269682] Call trace:
    [  210.272133]  dev_watchdog+0x234/0x240     [  210.275811]  call_timer_fn+0x3c/0x15c     [  210.279489]  __run_timers.part.0+0x288/0x310     [  210.283777]  run_timer_softirq+0x48/0x80     [  210.287716]  __do_softirq+0x128/0x360     [  210.291392]  __irq_exit_rcu+0x138/0x140     [  210.295243]  irq_exit_rcu+0x1c/0x30     [  210.298745]  el1_interrupt+0x38/0x54     [  210.302334]  el1h_64_irq_handler+0x18/0x24     [  210.306445]  el1h_64_irq+0x7c/0x80     [  210.309857]  arch_cpu_idle+0x18/0x2c     [  210.313445]  default_idle_call+0x4c/0x140     [  210.317470]  cpuidle_idle_call+0x14c/0x1a0     [  210.321584]  do_idle+0xb0/0x100     [  210.324737]  cpu_startup_entry+0x30/0x8c     [  210.328675]  secondary_start_kernel+0xe4/0x110     [  210.333138]  __secondary_switched+0x94/0x98

    The assumption when these were relaxed seems to be that device memory     would be mapped non reordering, and that other constructs     (spinlocks/etc) would provide the barriers to assure that packet data     and in memory rings/queues were ordered with respect to device     register reads/writes. This itself seems a bit sketchy, but the real     problem with GCC12 is that it is moving the actual reads/writes around     at will as though they were independent operations when in truth they     are not, but the compiler can't know that. When looking at the     assembly dumps for many of these routines its possible to see very     clean, but not strictly in program order operations occurring as the     compiler would be free to do if these weren't actually register     reads/write operations.

    Its possible to suppress the timeout with a liberal bit of dma_mb()'s     sprinkled around but the device still seems unable to reliably     send/receive data. A better plan is to use the safer readl/writel     everywhere.

    Since this partially reverts an older commit, which notes the use of     the relaxed variants for performance reasons. I would suggest that     any performance problems
    ---truncated---

Tenable has extracted the preceding description block directly from the Unity Linux security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote SUSE Linux SLES15 / SLES_SAP15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2025:1241-1 advisory.

    The SUSE Linux Enterprise 15 SP5 kernel was updated to receive various security bugfixes.

    The following security bugs were fixed:

    - CVE-2022-49053: scsi: target: tcmu: Fix possible page UAF (bsc#1237918).
    - CVE-2022-49465: blk-throttle: Set BIO_THROTTLED when bio has been throttled (bsc#1238919).
    - CVE-2022-49739: gfs2: Always check inode size of inline inodes (bsc#1240207).
    - CVE-2023-52935: mm/khugepaged: fix ->anon_vma race (bsc#1240276).
    - CVE-2024-53124: net: fix data-races around sk->sk_forward_alloc (bsc#1234074).
    - CVE-2024-53176: smb: During unmount, ensure all cached dir instances drop their dentry (bsc#1234894).
    - CVE-2024-53178: smb: Do not leak cfid when reconnect races with open_cached_dir (bsc#1234895).
    - CVE-2024-56651: can: hi311x: hi3110_can_ist(): fix potential use-after-free (bsc#1235528).
    - CVE-2024-57996: net_sched: sch_sfq: do not allow 1 packet limit (bsc#1239076).
    - CVE-2024-58013: Bluetooth: MGMT: Fix slab-use-after-free Read in mgmt_remove_adv_monitor_sync     (bsc#1239095).
    - CVE-2024-58014: wifi: brcmsmac: add gain range check to wlc_phy_iqcal_gainparams_nphy() (bsc#1239109).
    - CVE-2025-21693: mm: zswap: properly synchronize freeing resources during CPU hotunplug (bsc#1237029).
    - CVE-2025-21718: net: rose: fix timer races against user threads (bsc#1239073).
    - CVE-2025-21772: partitions: mac: fix handling of bogus partition table (bsc#1238911).
    - CVE-2025-21780: drm/amdgpu: avoid buffer overflow attach in smu_sys_set_pp_table() (bsc#1239115).


Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote SUSE Linux SLES15 / SLES_SAP15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2025:1027-1 advisory.

    The SUSE Linux Enterprise 15 SP4 kernel was updated to receive various security bugfixes.


    The following security bugs were fixed:

    - CVE-2024-2201: Fixed information leak in x86/BHI (bsc#1217339).
    - CVE-2024-41092: drm/i915/gt: Fix potential UAF by revoke of fence registers (bsc#1228483).
    - CVE-2024-42098: crypto: ecdh - explicitly zeroize private_key (bsc#1228779).
    - CVE-2024-42229: crypto: aead,cipher - zeroize key buffer after use (bsc#1228708).
    - CVE-2024-57996: net_sched: sch_sfq: do not allow 1 packet limit (bsc#1239076).
    - CVE-2024-58014: wifi: brcmsmac: add gain range check to wlc_phy_iqcal_gainparams_nphy() (bsc#1239109).
    - CVE-2025-21718: net: rose: fix timer races against user threads (bsc#1239073).
    - CVE-2025-21780: drm/amdgpu: avoid buffer overflow attach in smu_sys_set_pp_table() (bsc#1239115).


Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - net: bcmgenet: Use stronger register read/writes to assure ordering GCC12 appears to be much smarter about     its dependency tracking and is aware that the relaxed variants are just normal loads and stores and this     is causing problems like: [ 210.074549] ------------[ cut here ]------------ [ 210.079223] NETDEV     WATCHDOG: enabcm6e4ei0 (bcmgenet): transmit queue 1 timed out [ 210.086717] WARNING: CPU: 1 PID: 0 at     net/sched/sch_generic.c:529 dev_watchdog+0x234/0x240 [ 210.095044] Modules linked in: genet(E)     nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject     nft_ct nft_chain_nat] [ 210.146561] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [ 210.146927]     CPU: 1 PID: 0 Comm: swapper/1 Tainted: G E 5.17.0-rc7G12+ #58 [ 210.153226] CPPC     Cpufreq:cppc_scale_freq_workfn: failed to read perf counters [ 210.161349] Hardware name: Raspberry Pi     Foundation Raspberry Pi 4 Model B/Raspberry Pi 4 Model B, BIOS EDK2-DEV 02/08/2022 [ 210.161353] pstate:
    80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 210.161358] pc : dev_watchdog+0x234/0x240 [     210.161364] lr : dev_watchdog+0x234/0x240 [ 210.161368] sp : ffff8000080a3a40 [ 210.161370] x29:
    ffff8000080a3a40 x28: ffffcd425af87000 x27: ffff8000080a3b20 [ 210.205150] x26: ffffcd425aa00000 x25:
    0000000000000001 x24: ffffcd425af8ec08 [ 210.212321] x23: 0000000000000100 x22: ffffcd425af87000 x21:
    ffff55b142688000 [ 210.219491] x20: 0000000000000001 x19: ffff55b1426884c8 x18: ffffffffffffffff [     210.226661] x17: 64656d6974203120 x16: 0000000000000001 x15: 6d736e617274203a [ 210.233831] x14:
    2974656e65676d63 x13: ffffcd4259c300d8 x12: ffffcd425b07d5f0 [ 210.241001] x11: 00000000ffffffff x10:
    ffffcd425b07d5f0 x9 : ffffcd4258bdad9c [ 210.248171] x8 : 00000000ffffdfff x7 : 000000000000003f x6 :
    0000000000000000 [ 210.255341] x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000001000 [     210.262511] x2 : 0000000000001000 x1 : 0000000000000005 x0 : 0000000000000044 [ 210.269682] Call trace: [     210.272133] dev_watchdog+0x234/0x240 [ 210.275811] call_timer_fn+0x3c/0x15c [ 210.279489]
    __run_timers.part.0+0x288/0x310 [ 210.283777] run_timer_softirq+0x48/0x80 [ 210.287716]
    __do_softirq+0x128/0x360 [ 210.291392] __irq_exit_rcu+0x138/0x140 [ 210.295243] irq_exit_rcu+0x1c/0x30 [     210.298745] el1_interrupt+0x38/0x54 [ 210.302334] el1h_64_irq_handler+0x18/0x24 [ 210.306445]     el1h_64_irq+0x7c/0x80 [ 210.309857] arch_cpu_idle+0x18/0x2c [ 210.313445] default_idle_call+0x4c/0x140 [     210.317470] cpuidle_idle_call+0x14c/0x1a0 [ 210.321584] do_idle+0xb0/0x100 [ 210.324737]     cpu_startup_entry+0x30/0x8c [ 210.328675] secondary_start_kernel+0xe4/0x110 [ 210.333138]
    __secondary_switched+0x94/0x98 The assumption when these were relaxed seems to be that device memory would     be mapped non reordering, and that other constructs (spinlocks/etc) would provide the barriers to assure     that packet data and in memory rings/queues were ordered with respect to device register reads/writes.
    This itself seems a bit sketchy, but the real problem with GCC12 is that it is moving the actual     reads/writes around at will as though they were independent operations when in truth they are not, but the     compiler can't know that. When looking at the assembly dumps for many of these routines its possible to     see very clean, but not strictly in program order operations occurring as the compiler would be free to do     if these weren't actually register reads/write operations. Its possible to suppress the timeout with a     liberal bit of dma_mb()'s sprinkled around but the device still seems unable to reliably send/receive     data. A better plan is to use the safer readl/writel everywhere. Since this partially reverts an older     commit, which notes the use of the relaxed variants for performance reasons. I would suggest that any     performance problems ---truncated--- (CVE-2022-49194)

Note that Nessus relies on the presence of the package as reported by the vendor.

ID	Name	Product	Family	Severity
273295	Unity Linux 20.1070a Security Update: kernel (UTSA-2025-988688)	Nessus	Unity Linux Local Security Checks	medium
273032	Unity Linux 20.1070e Security Update: kernel (UTSA-2025-989592)	Nessus	Unity Linux Local Security Checks	medium
234407	SUSE SLES15 Security Update : kernel (SUSE-SU-2025:1241-1)	Nessus	SuSE Local Security Checks	high
233410	SUSE SLES15 Security Update : kernel (SUSE-SU-2025:1027-1)	Nessus	SuSE Local Security Checks	high
225360	Linux Distros Unpatched Vulnerability : CVE-2022-49194	Nessus	Misc.	medium

Detections

Analytics

CVE-2022-49194

medium

Tenable Plugins

medium

medium

high

high

medium