Chinese Salt Typhoon Infiltrated US National Guard Network for Months
Source: https://hackread.com/chinese-salt-typhoon-infiltrated-us-national-guard-network/
Salt Typhoon breach: Chinese APT compromises U.S. Army National Guard network
Source: https://securityaffairs.com/180018/intelligence/salt-typhoon-breach-chinese-apt-compromises-u-s-army-national-guard-network.html
In the Linux kernel, the following vulnerability has been resolved: net: dsa: mv88e6xxx: fix -ENOENT when deleting VLANs and MST is unsupported Russell King reports that on the ZII dev rev B, deleting a bridge VLAN from a user port fails with -ENOENT: https://lore.kernel.org/netdev/Z_lQXNP0s5-IiJzd@shell.armlinux.org.uk/ This comes from mv88e6xxx_port_vlan_leave() -> mv88e6xxx_mst_put(), which tries to find an MST entry in &chip->msts associated with the SID, but fails and returns -ENOENT as such. But we know that this chip does not support MST at all, so that is not surprising. The question is why does the guard in mv88e6xxx_mst_put() not exit early: if (!sid) return 0; And the answer seems to be simple: the sid comes from vlan.sid which supposedly was previously populated by mv88e6xxx_vtu_get(). But some chip->info->ops->vtu_getnext() implementations do not populate vlan.sid, for example see mv88e6185_g1_vtu_getnext(). In that case, later in mv88e6xxx_port_vlan_leave() we are using a garbage sid which is just residual stack memory. Testing for sid == 0 covers all cases of a non-bridge VLAN or a bridge VLAN mapped to the default MSTI. For some chips, SID 0 is valid and installed by mv88e6xxx_stu_setup(). A chip which does not support the STU would implicitly only support mapping all VLANs to the default MSTI, so although SID 0 is not valid, it would be sufficient, if we were to zero-initialize the vlan structure, to fix the bug, due to the coincidence that a test for vlan.sid == 0 already exists and leads to the same (correct) behavior. Another option which would be sufficient would be to add a test for mv88e6xxx_has_stu() inside mv88e6xxx_mst_put(), symmetric to the one which already exists in mv88e6xxx_mst_get(). But that placement means the caller will have to dereference vlan.sid, which means it will access uninitialized memory, which is not nice even if it ignores it later. So we end up making both modifications, in order to not rely just on the sid == 0 coincidence, but also to avoid having uninitialized structure fields which might get temporarily accessed.
CVE-2024-57949 is a medium severity vulnerability in the Linux kernel's irqchip/gic-v3-its component. It involves improper handling of interrupt enabling in the its_irq_set_vcpu_affinity() function, where interrupts are enabled inside a nested interrupt-disabled section due to a code change. This can lead to a warning and potential instability. The issue was introduced by a commit replacing raw_spin_lock/unlock with a guard that incorrectly enables interrupts. The fix involves using the correct guard to avoid enabling interrupts prematurely.
CVE-2024-49856 is a vulnerability in the Linux kernel's x86 SGX (Software Guard Extensions) implementation. It involves a deadlock condition in the NUMA node search for EPC (Enclave Page Cache) memory. If the current NUMA node lacks an EPC section configured by firmware and all other EPC sections are fully used, the CPU can become stuck in an indefinite loop, causing a soft lockup. This issue arises because the search loop never encounters the current node in the SGX memory mask, leading to deadlock. The vulnerability has been fixed by reworking the loop to avoid this deadlock scenario.
Red Hat issued a security advisory for java-17-openjdk packages addressing multiple vulnerabilities in OpenJDK 17. These include an array out-of-bounds access in the C1 compiler, incorrect handling of ZIP files with duplicate entries, an RSA padding and timing side-channel issue affecting TLS, a JVM class file verifier flaw allowing unverified bytecode execution, a range check loop optimization issue, and logging of digital signature private keys. Additionally, a bug fix addresses excessive memory usage caused by Transparent Huge Pages (THP) interaction with JVM guard pages. The update is rated as important by Red Hat and requires restarting all running OpenJDK Java instances to apply the fixes.