Tinxy WiFi Lock Controller v1 RF 安全漏洞

Tinxy WiFi Lock Controller v1 RF is a smart door lock from Tinxy. A security vulnerability exists in Tinxy WiFi Lock Controller v1 RF, which originates from transmitting sensitive information in clear text and could lead to a man-in-the-middle attack...

CVE-2025-44614

Tinxy WiFi Lock Controller v1 RF was discovered to store users' sensitive information, including credentials and mobile phone numbers, in plaintext...

Tinxy WiFi Lock Controller v1 RF 访问控制错误漏洞

Tinxy WiFi Lock Controller v1 RF is a smart door lock from Tinxy. A security vulnerability exists in the Tinxy WiFi Lock Controller v1 RF, which originates from being configured for an open Wi-Fi network and could lead to unauthenticated network access...

PT-2025-23235

Name of the Vulnerable Software and Affected Versions Tinxy WiFi Lock Controller version v1 RF Description The issue allows attackers to join the network without authentication because the device is configured to transmit on an open Wi-Fi network. Recommendations For Tinxy WiFi Lock Controller...

DEBIAN-CVE-2025-37999

In the Linux kernel, the following vulnerability has been resolved: fs/erofs/fileio: call erofsonlinefoliosplit after bioaddfolio If bioaddfolio fails because it is full, erofsfileioscanfolio needs to submit the I/O request via erofsfileiorqsubmit and allocate a new I/O request with an empty stru...

DEBIAN-CVE-2025-37993

In the Linux kernel, the following vulnerability has been resolved: can: mcan: mcanclassallocatedev: initialize spin lock on device probe The spin lock txhandlingspinlock in struct mcanclassdev is not being initialized. This leads the following spinlock bad magic complaint from the kernel, eg. wh...

CVE-2025-37993

In the Linux kernel, the following vulnerability has been resolved: can: mcan: mcanclassallocatedev: initialize spin lock on device probe The spin lock txhandlingspinlock in struct mcanclassdev is not being initialized. This leads the following spinlock bad magic complaint from the kernel, eg. wh...

CVE-2025-37999

The CVE-2025-37999 issue affects the Linux kernel's EROFS fileio path. When bio_add_folio() fails, erofs_fileio_scan_folio() submits a new I/O request and retries with an empty bio, but erofs_onlinefolio_split() had already run, incrementing folio->private. The retry then calls erofs_onlinefol...

CVE-2025-37999 fs/erofs/fileio: call erofs_onlinefolio_split() after bio_add_folio()

In the Linux kernel, the following vulnerability has been resolved: fs/erofs/fileio: call erofsonlinefoliosplit after bioaddfolio If bioaddfolio fails because it is full, erofsfileioscanfolio needs to submit the I/O request via erofsfileiorqsubmit and allocate a new I/O request with an empty stru...

CVE-2025-37993 can: m_can: m_can_class_allocate_dev(): initialize spin lock on device probe

In the Linux kernel, the following vulnerability has been resolved: can: mcan: mcanclassallocatedev: initialize spin lock on device probe The spin lock txhandlingspinlock in struct mcanclassdev is not being initialized. This leads the following spinlock bad magic complaint from the kernel, eg. wh...

CVE-2025-37993

CVE-2025-37993 refers to a Linux kernel issue where the m_can_classdev.tx_handling_spinlock was not initialized during device probe, causing a spinlock bad magic crash (notably when cansend is used). The problem is resolved by initializing the spin lock in m_can_class_allocate_dev. Affected conte...

CVE-2025-37993 can: m_can: m_can_class_allocate_dev(): initialize spin lock on device probe

In the Linux kernel, the following vulnerability has been resolved: can: mcan: mcanclassallocatedev: initialize spin lock on device probe The spin lock txhandlingspinlock in struct mcanclassdev is not being initialized. This leads the following spinlock bad magic complaint from the kernel, eg. wh...

PT-2025-23152 · Linux +1 · Linux Kernel +1

Name of the Vulnerable Software and Affected Versions: Linux kernel versions prior to 6.15.0-rc3 Description: A vulnerability in the Linux kernel has been resolved, related to the initialization of a spin lock in the m can classdev struct. The issue occurs when trying to send CAN frames, resultin...

kernel: sched/rt: Fix race in push_rt_task

In the Linux kernel, the following vulnerability has been resolved: sched/rt: Fix race in pushrttask Overview ======== When a CPU chooses to call pushrttask and picks a task to push to another CPU's runqueue then it will call findlocklowestrq method which would take a double lock on both CPUs'...

PT-2025-27715

Name of the Vulnerable Software and Affected Versions: Linux kernel versions prior to 6.13.0-rc3-syzkaller-gdfa94ce54f41 Description: A use-after-free issue has been identified in the Linux kernel, specifically in the page pool recycle in ring function. This issue was reported by syzbot and is...

CVE-2025-4053

Be-Tech Mifare Classic card systems are affected. The root cause is that data stored on the Mifare Classic cards is in cleartext, enabling an attacker with a guest card to craft a master key card that can unlock all locks in the building. Affected component: Be-Tech Mifare Classic cards and assoc...

GHSA-6V24-6WGF-8VJ6 process_lock has a Potential Unsound issue in unlock

The processlock crate 0.1.0 for Rust allows data races in unlock...

CVE-2025-48751

The processlock crate 0.1.0 for Rust allows data races in unlock...

PT-2025-22828 · Unknown · Process Lock

Name of the Vulnerable Software and Affected Versions: process lock crate version 0.1.0 Description: The issue allows data races in unlock, which can lead to unpredictable behavior. Recommendations: For process lock crate version 0.1.0, consider avoiding the use of the unlock functionality until ...

CVE-2025-48751

CVE-2025-48751 involves the Rust crate process_lock version 0.1.0. The available documents describe a race condition in the unlock pathway that can lead to data races and potentially unpredictable behavior. Concrete details across sources confirm the affected component (the unlock logic in the pr...