Skip to main content

Threats Tagged 'cve-2026-63965'

View all threats tagged with 'cve-2026-63965'. Filter and sort to focus on specific types of threats.

Pro Console Lifetime

Stop chasing alerts. Route them.

Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.

Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)

View Plans & Pricing

API access activates after upgrading in Console -> Billing.

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now

Filter Threats

Narrow down the results by type, severity, or affected countries

Search threats by title, CVE ID, or description. Maximum 100 characters.
Active filters (1):Tag: cve-2026-63965

Threats Tagged 'cve-2026-63965'

Click on any threat for detailed analysis and mitigation recommendations

In the Linux kernel, the following vulnerability has been resolved: iio: pressure: bmp280: fix stack leak in bmp580 trigger handler bmp580_trigger_handler() declares its scan buffer on the stack without an initializer and then memcpy()s 3 bytes of 24-bit sensor data into each 4-byte __le32 field. The high byte of comp_temp and comp_press is left uninitialized, and the channel storagebits is 32, so two bytes of stack are pushed to userspace per scan. This is a regression from when the buffer lived in the private data, the move to a stack-local struct dropped the implicit zeroing. bme280_trigger_handler() was fixed up to handle this bug, but this driver was not fixed because there was no padding hole, but rather a short-fill issue. Fix this all by just zero-initializing the structure on the stack.

Join the discussion

A vulnerability in the Linux kernel's bmp280 pressure sensor driver involves uninitialized stack memory in the bmp580 trigger handler. The handler copies 3 bytes of sensor data into a 4-byte field on the stack without zero-initializing the buffer, leaving the high byte uninitialized. This causes two bytes of potentially sensitive stack data to be exposed to userspace per scan. The issue is a regression caused by moving the buffer from private data to a stack-local structure without zeroing it. The vulnerability has been resolved by zero-initializing the stack structure.

Join the discussion

Showing 1 to 2 of 2 results

Filters:Tag: cve-2026-63965
Page 1 of 1
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses