Search

Search Results (429957 CVEs found)

CVE Vendors Products Updated CVSS v3.1
CVE-2026-99695 1 Linux 2 Linux, Linux Kernel 2026-11-20 N/A
In the Linux kernel, the following vulnerability has been resolved: ocfs2: find the xattr entry again after converting a block to a bucket ocfs2_xattr_create_index_block() turns a non-indexed xattr block into a tree by copying it into a bucket, and the copy sorts the entries: a block holds them in insertion order, a bucket by name hash. ocfs2_xattr_update_xattr_search() nevertheless relocates the caller's search by the index the entry had in the block, so unless the two orders agreed it points at an unrelated entry, and nothing between there and the write compares that entry's name with the one being set. Setting an xattr whose new value no longer fits the block arrives here with xs->not_found clear. The block gave up because ocfs2_xa_block_can_reuse() wants an exact namevalue size match, while ocfs2_xa_bucket_can_reuse() only wants an entry at least as large as the new one, so the bucket accepts a pair the block rejected and the update lands on whichever entry the sort left at that index. Equal padded name lengths get that other attribute's value replaced in place and its name left alone, so setxattr returns success while the attribute asked for keeps its old value. A longer one trips ocfs2_xa_reuse_entry()'s BUG_ON, and a shorter one is refused by the bucket as well, so ocfs2_xa_prepare_entry() wipes the entry and writes the new name over it, leaving xe_name_hash describing a name that is no longer there. Find the entry again by the name being set, matching the type as well. The copy carries every entry and every name over unchanged, and (type, name) pairs are unique within a block, so the match is exact. The type matters because the handlers strip their prefix before calling ocfs2_xattr_set(), so user.foo and trusted.foo share a stored name, a stored length and a hash, and both can sit in the same block. The name has to come from xi rather than from xs->here: a failed set can remove the entry xs->here names, and only the "growing" caller sets ctxt->set_abort, which is what stops the conversion. Scan every entry rather than narrowing on the hash the way ocfs2_find_xe_in_bucket() does, since an existing entry keeps the hash it was stored under, which a kernel that sign-extended the name bytes made different from the one computed now. An empty result means the entry did not survive the failed set and this has become an insert; leaving xs->here alone would keep it pointing into the block, which is rewritten as a tree root before the caller reads it again.
CVE-2026-99718 1 Linux 2 Linux, Linux Kernel 2026-11-20 4.1 Medium
In the Linux kernel, the following vulnerability has been resolved: hwmon: (peci/dimmtemp) Fix devres leak and UAF on concurrent unbind When a peci_dimmtemp device is unbound concurrently with its delayed initialization work (detect_work), newly allocated devm resources and the hwmon device are leaked, leading to a use-after-free when reading the lingering hwmon sysfs attributes. In peci_dimmtemp_probe(), detect_work is registered for cancellation via devm_delayed_work_autocancel(). During driver detach, devres_release_all() first moves all existing entries from dev->devres_head onto a local todo list before invoking their release callbacks in reverse order. If create_dimm_temp_info_delayed() is already running when devm_delayed_work_drop() calls cancel_delayed_work_sync(), create_dimm_temp_info() can allocate dimmtemp_label strings via devm_kzalloc()/devm_kasprintf() and register the hwmon device via devm_hwmon_device_register_with_info(), appending new devres entries to the now-empty dev->devres_head. Once the work finishes, devres_release_all() frees priv and priv->name from the local todo list without re-evaluating dev->devres_head, leaving the late devres allocations and registered hwmon device behind with a dangling priv pointer. Cancel detect_work synchronously in a driver .remove() callback instead of relying on devm_delayed_work_autocancel() so that the work is fully drained before devres_release_all() detaches dev->devres_head, allowing any devm resources registered by the delayed work to be released in proper reverse order. Also only schedule detect_work when check_populated_dimms() returns -EAGAIN so that probe failure paths do not leave delayed work pending.
CVE-2026-99719 1 Linux 2 Linux, Linux Kernel 2026-11-20 5.6 Medium
In the Linux kernel, the following vulnerability has been resolved: hwmon: (lm87) Fix drvdata type confusion in vrm_show() and vrm_store() When an LM87 or ADM1024 device is probed with VID support enabled, reading from or writing to the vrm sysfs attribute triggers a driver data type confusion in vrm_show() and vrm_store() in drivers/hwmon/lm87.c. In lm87_probe(), the driver stores the struct lm87_data pointer on the I2C client via i2c_set_clientdata() and passes the struct i2c_client pointer as the drvdata argument to devm_hwmon_device_register_with_groups(), which attaches the attribute groups to the registered hwmon device with client as its driver_data. Unlike the other sysfs callbacks that retrieve client via dev_get_drvdata() and then obtain data via i2c_get_clientdata(), vrm_show() and vrm_store() assign dev_get_drvdata(dev) directly to struct lm87_data *. Dereferencing data->vrm therefore accesses the struct i2c_client instance at offsetof(struct lm87_data, vrm), causing vrm_show() to leak an unrelated byte from struct i2c_client to userspace and vrm_store() to corrupt a byte within struct i2c_client while failing to update the actual VRM value. Fix the problem by assigning the return value from dev_get_drvdata(dev) to struct i2c_client *client and using i2c_get_clientdata() to get the actual client data.
CVE-2026-99720 1 Linux 2 Linux, Linux Kernel 2026-11-20 N/A
In the Linux kernel, the following vulnerability has been resolved: hwmon: chipcap2: fix IRQ teardown ordering The threaded IRQs are currently requested before the hwmon device is registered. Since devres releases resources in reverse order, the hwmon device is unregistered before the IRQs are freed during driver teardown. An IRQ may therefore still run after the hwmon device has been released and access the stale data->hwmon pointer. Separate IRQ discovery from IRQ registration so that the IRQ numbers and alarm visibility flags are initialized before registering the hwmon device while the IRQs are released before the hwmon device during devres cleanup.
CVE-2026-99721 1 Linux 2 Linux, Linux Kernel 2026-11-20 N/A
In the Linux kernel, the following vulnerability has been resolved: hwmon: (aquacomputer_d5next) reject short status reports The HID raw_event callback runs before HID core validates the received report length. aqc_raw_event() reads device-specific status fields at fixed offsets, including multi-byte values, without first ensuring that the received buffer contains every field. A truncated report can therefore cause out-of-bounds reads and update hwmon state with unrelated data. The required length differs between supported devices and cannot be derived from the HID report descriptor. Define the minimum length needed by each asynchronous status format, select it while configuring the device, and reject reports that do not contain the last field accessed by that format. Keep the published length zero until probe configuration is complete, which also excludes legacy devices whose status is retrieved through feature reports.
CVE-2026-99726 1 Linux 2 Linux, Linux Kernel 2026-11-20 N/A
In the Linux kernel, the following vulnerability has been resolved: drm/v3d: Widen cache_clean_lock over the whole L2TCACTL sequence v3d_clean_caches() and v3d_flush_l2t() both write the single L2TCACTL register and poll its status bits. The mutex cache_clean_lock exists to serialize them, but v3d_clean_caches() only took the lock around its final FLM_CLEAN write. These functions run concurrently: v3d_flush_l2t() is issued from the BIN/RENDER/CSD invalidate path while v3d_clean_caches() runs from the CACHE_CLEAN queue, and each queue's scheduler uses its own ordered workqueue, so their run_job callbacks execute in parallel. Because clean locked only its final write, a concurrent flush can write L2TCACTL during clean's unlocked phase. Both use non read-modify-write writes to the one register, so whichever lands last wins: clean's TMUWCF write can land on the flush's in-flight L2TFLS invalidate, triggering the GFXH-1897 hazard of writing L2TCACTL while a flush is pending. Hold cache_clean_lock across the entire L2TCACTL access sequence so it is fully mutually exclusive with v3d_flush_l2t(), which already takes the lock around its own write.
CVE-2026-101340 2026-11-20 N/A
Net::DNS uses a 16-bit query ID to match responses to the corresponding requests. In versions up to and including 1.57, the ID is obtained from Perl's built-in rand() function. An attacker that can observe the sequence of query IDs is able to expose the internal state of the PNRG and hence predict query IDs before they are transmitted. The victim Net::DNS instance is then exposed to forged responses injected by the attacker. Note that the deduplication cache in 1.57 has no impact on the feasibility of this attack.
CVE-2026-130669 1 Imagemagick 1 Imagemagick 2026-11-20 3.3 Low
ImageMagick before 7.1.2-35 contains a null pointer dereference vulnerability that allows attackers to crash the process by using the -subimage option on a single-image list. Attackers can supply input producing an image list with only one image while -subimage is applied, causing a denial of service.
CVE-2026-129420 2026-11-20 N/A
Joomla Extension - joomlatools.com - Local file read through remote document links in DOCman extension < 6.2.2 - Remote document links accepted the file:// scheme, allowing users with permission to create or edit documents to download arbitrary local files from the server, such as the Joomla configuration file.
CVE-2026-133606 1 Powerjob 1 Powerjob 2026-11-20 5.3 Medium
A weakness has been identified in PowerJob up to 5.1.7. This affects the function CustomHttpServletRequestWrapper of the file powerjob-server/powerjob-server-starter/src/main/java/tech/powerjob/server/config/CachingRequestBodyFilter.java of the component CachingRequestBodyFilter. Executing a manipulation can lead to denial of service. It is possible to launch the attack remotely.
CVE-2026-111517 1 Dell 1 Alienware Command Center 2026-11-20 4.4 Medium
Dell Alienware Command Center (AWCC), versions prior to 6.14.105.0, contain a Deserialization of Untrusted Data vulnerability. A low privileged attacker with local access could potentially exploit this vulnerability, leading to Arbitrary Code Execution.
CVE-2026-111516 1 Dell 1 Alienware Command Center 2026-11-20 6.6 Medium
Dell Alienware Command Center (AWCC), versions prior to 6.14.105.0, contain a Least Privilege Violation vulnerability. A low privileged attacker with local access could potentially exploit this vulnerability, leading to Elevation of Privilege and Denial of Service.
CVE-2026-111518 1 Dell 1 Alienware Command Center 2026-11-20 3.1 Low
Dell Alienware Command Center (AWCC), versions prior to 6.14.105.0, contain an Improper Restriction of Rendered UI Layers or Frames vulnerability. A high privileged attacker with remote access could potentially exploit this vulnerability, leading to Denial of Service and Launch of Phishing Attacks.
CVE-2026-111519 1 Dell 1 Alienware Command Center 2026-11-20 2 Low
Dell Alienware Command Center (AWCC), versions prior to 6.14.105.0, contain an Improper Authorization in Handler for Custom URL Scheme vulnerability. A high privileged attacker with remote access could potentially exploit this vulnerability, leading to Client-Side Request Forgery and Information Disclosure.
CVE-2026-111515 1 Dell 1 Alienware Command Center 2026-11-20 7.1 High
Dell Alienware Command Center (AWCC), versions prior to 6.14.105.0, contain an Improper Authorization in Handler for Custom URL Scheme vulnerability. An unauthenticated attacker with remote access could potentially exploit this vulnerability, leading to Command Execution and Launch of Phishing Attacks.
CVE-2026-132199 2026-11-20 6.6 Medium
A flaw was found in flac. When a size-changing metadata edit is performed on a FLAC file that is a symbolic link with a relative target, libFLAC renames the edited temporary file to the raw link-target string, which the operating system resolves against the process working directory instead of the directory containing the link. An attacker who can place a relative symlink and a co-located FLAC file in a location a victim will edit could use this to cause the victim's routine metadata edit to overwrite files relative to the victim's working directory, destroying the original content.
CVE-2026-133195 1 Jetbrains 1 Junie Cli 2026-11-20 7.5 High
In JetBrains Junie CLI before 26.6.29 files outside the project directory could be modified by agent file tools
CVE-2026-121584 1 Mattermost 1 Mattermost 2026-11-20 6.5 Medium
Mattermost versions 11.7.x <= 11.7.11, 11.10.x <= 11.10.2, 11.11.x <= 11.11.1 fail to bound the number of records a single GraphQL request may hydrate which allows an authenticated user to exhaust server memory and cause a denial of service via a small query that repeats the runs field under many aliases. Mattermost Advisory ID: MMSA-2026-00767
CVE-2026-102770 1 Neo4j 2 Enterprise Edition, Neo4j 2026-11-20 N/A
Improper neutralization of special elements in data query logic (Cypher injection) in the fulltext and vector index query generator of the sharded property database in Neo4j Enterprise Edition 2026.07.0 before 2026.10.0 allows an authenticated user holding ACCESS, CREATE INDEX and NAME MANAGEMENT privileges to inject Cypher that is accepted for execution on a property shard, in the session of any user who later queries the index, via a crafted index name containing a single quote. The impact is bounded by the privileges of the querying user.
CVE-2026-121594 1 Mattermost 1 Mattermost 2026-11-20 5.3 Medium
Mattermost Plugins versions <=12.-1 11.11.7 11.2.10 11.1.11.0 fail to enforce the GitLab project permission check for confidential issues when the project is publicly visible which allows an authenticated user with no GitLab membership in the project to obtain the contents of confidential issues, including title, description, author, and URL via subscribing a channel to the parent public GitLab group with the confidential_issues feature and waiting for a confidential issue webhook event. Mattermost Advisory ID: MMSA-2026-00738