CVSS 3.1 base metricsRed raises the risk · green lowers it
Attack vector
LocalAV:L
Attack complexity
LowAC:L
Privileges required
LowPR:L
User interaction
NoneUI:N
Scope
UnchangedS:U
Confidentiality
NoneC:N
Integrity
NoneI:N
Availability
HighA:H
Updates that fix it
0 KBs
No KB listed
No KB update is listed in the collected MSRC record. Check the MSRC advisory for product releases and other remedies.
Affected products
Open Source Software
5 affected products
azl3 kernel 6.6.150.1-1 on Azure Linux 3.0
azl3 kernel 6.6.152.1-1 on Azure Linux 3.0
azl3 kernel 6.6.157.1-1 on Azure Linux 3.0
azl3 kernel 6.6.159.1-1 on Azure Linux 3.0
azl3 kernel 6.6.161.1-1 on Azure Linux 3.0
What changed
Detection template: Unknown: detection-template evidence is incomplete or retained → No Nuclei template listed
Detection template: No Nuclei template listed → Unknown: detection-template evidence is incomplete or retained
Affected products: azl3 kernel 6.6.150.1-1 on Azure Linux 3.0, azl3 kernel 6.6.152.1-1 on Azure Linux 3.0, azl3 kernel 6.6.157.1-1 on Azure Linux 3.0, azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 → azl3 kernel 6.6.150.1-1 on Azure Linux 3.0, azl3 kernel 6.6.152.1-1 on Azure Linux 3.0, azl3 kernel 6.6.157.1-1 on Azure Linux 3.0, azl3 kernel 6.6.159.1-1 on Azure Linux 3.0, azl3 kernel 6.6.161.1-1 on Azure Linux 3.0
Detection template: Unknown: detection-template evidence is incomplete or retained → No Nuclei template listed
Detection template: No Nuclei template listed → Unknown: detection-template evidence is incomplete or retained
Affected products: azl3 kernel 6.6.150.1-1 on Azure Linux 3.0, azl3 kernel 6.6.152.1-1 on Azure Linux 3.0, azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 → azl3 kernel 6.6.150.1-1 on Azure Linux 3.0, azl3 kernel 6.6.152.1-1 on Azure Linux 3.0, azl3 kernel 6.6.157.1-1 on Azure Linux 3.0, azl3 kernel 6.6.159.1-1 on Azure Linux 3.0
Detection template: No Nuclei template listed · Customer action: Required: apply the update → Required: follow the MSRC remediation guidance · Public disclosure: No → Unknown: not stated by MSRC · Exploitation detected: Not reported by MSRC → Unknown: not stated by MSRC
Detection template: Unknown: exploit-code evidence is incomplete or retained → No Nuclei template listed · CISA KEV: Unknown: catalog evidence is incomplete or retained → Not listed in the collected catalog
Detection template: No Nuclei template listed → Unknown: exploit-code evidence is incomplete or retained · CISA KEV: Not listed in the collected catalog → Unknown: catalog evidence is incomplete or retained
Page history
Changes are dated when recorded; day views use the last saved version from that UTC day, and citations stay fixed.
6 Nov 2026 · 09:07:49 UTCAffected productsazl3 kernel 6.6.150.1-1 on Azure Linux 3.0, azl3 kernel 6.6.152.1-1 on Azure Linux 3.0, azl3 kernel 6.6.157.1-1 on Azure Linux 3.0, azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 → azl3 kernel 6.6.150.1-1 on Azure Linux 3.0, azl3 kernel 6.6.152.1-1 on Azure Linux 3.0, azl3 kernel 6.6.157.1-1 on Azure Linux 3.0, azl3 kernel 6.6.159.1-1 on Azure Linux 3.0, azl3 kernel 6.6.161.1-1 on Azure Linux 3.0
2 Nov 2026 · 17:30:39 UTCPublic detection templateUnknown: detection-template evidence is incomplete or retained → No Nuclei template listed
2 Nov 2026 · 09:04:36 UTCAffected productsazl3 kernel 6.6.150.1-1 on Azure Linux 3.0, azl3 kernel 6.6.152.1-1 on Azure Linux 3.0, azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 → azl3 kernel 6.6.150.1-1 on Azure Linux 3.0, azl3 kernel 6.6.152.1-1 on Azure Linux 3.0, azl3 kernel 6.6.157.1-1 on Azure Linux 3.0, azl3 kernel 6.6.159.1-1 on Azure Linux 3.0
CISA KEV is observed exploitation evidence. FIRST EPSS is a dated prediction of exploitation in the next 30 days. Missing scores are unknown. This collector requests predictions only for explicit CVE aliases in the public NuGet archive; Microsoft release views retain their existing prediction scope.
No collected risk observation for these identifiers. This does not establish absence of exploitation or a zero probability.
cve-program · CVE-2026-93047
Published
drm/v3d: Associate BOs with every job that accesses them
In the Linux kernel, the following vulnerability has been resolved:
drm/v3d: Associate BOs with every job that accesses them
A submission can expand into a chain of jobs (e.g. bin + render + cache
clean). Implicit synchronization in v3d_submit_lock_reservations() is gated
on each job's bo[], but the BO list was only ever attached to the last job
of the chain. When that last job is a trailing CACHE_CLEAN job, the job
that actually consumes the BOs (that is, a RENDER or CSD job) was left with
bo_count == 0 and picked up no implicit dependencies. It could therefore
be dispatched to the hardware and read a BO while another context was still
writing it, leading to data corruption.
Attach the BOs to the job that consumes them, so (1) it acquires the
correct implicit dependencies during reservation locking and (2) they are
kept mapped until the end of the submission. Give it references to all
consuming job's BOs through v3d_job_reference_bos() instead of looking the
handles up a second time; that avoids a redundant lookup and guarantees
both jobs reference the exact same objects.
As the CACHE_CLEAN job now carries a BO array as well, add a per-job
`has_implicit_dep` flag so that only the consuming jobs take implicit
dependencies. The CACHE_CLEAN job (a global flush) and the BIN job (binning
waiting on another context is not a realistic scenario) are excluded.
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: cve-program · CVE Program Terms of Use. Source text is retained; field grouping and change labels are provided by ChangeIntel.