Fallos del tipo CWE-667

181 resultados

Sincronização inadequada de acesso a recursos compartilhados

Ocorre quando código que acessa dados ou recursos compartilhados (variáveis globais, arquivos, conexões de banco) não usa mecanismos adequados de sincronização (locks, mutexes, semáforos). Isso permite que múltiplas threads ou processos modifiquem o mesmo recurso simultaneamente, causando corrupção de dados, valores inconsistentes ou comportamento impredizível.

Ejemplo

Uma aplicação multi-thread que incrementa um contador sem lock: duas threads podem ler o valor 100 ao mesmo tempo, incrementar para 101, e ambas escreverem 101 — perdendo uma unidade de incremento. Ou pior: um banco de dados que aceita duas conexões simultâneas atualizando o mesmo saldo, resultando em estados inconsistentes.

Cómo mitigar

Use mutex/lock ao acessar dados compartilhados; prefira estruturas thread-safe da linguagem (ConcurrentHashMap em Java, locks em Python); minimize o escopo e duração de seções críticas; valide e teste cenários de concorrência com ferramentas de análise estática.

CVE-2025-39832MEDIUMnet/mlx5: Fix lockdep assertion on sync reset unload eventEPSS 0.1%CVE-2026-118052MEDIUMModule Manager loaders leave the manager mutex held when a module preamble's sizes overflow, blocking every later module operationEPSS 0.1%CVE-2025-39884MEDIUMbtrfs: fix subvolume deletion lockup caused by inodes xarray raceEPSS 0.1%CVE-2026-43211HIGHPCI: Fix pci_slot_trylock() error handlingEPSS 0.1%CVE-2025-20044MEDIUMImproper locking for some Intel(R) TDX Module firmware before version 1.5.13 may allow a privileged user to potentially enable escalation ofEPSS 0.1%CVE-2026-46107HIGHdm-thin: fix metadata refcount underflowEPSS 0.1%CVE-2025-39915MEDIUMnet: phy: transfer phy_config_inband() locking responsibility to phylinkEPSS 0.1%CVE-2026-47581MEDIUMNVIDIA GPU Display Driver for Windows contains a vulnerability in the kernel module where a user could cause improper locking. A successful EPSS 0.1%CVE-2026-56914HIGHIn multiple locations, there is a possible use-after-free due to improper locking. This could lead to local escalation of privilege with no EPSS 0.1%CVE-2023-20619MEDIUMIn vcu, there is a possible memory corruption due to improper locking. This could lead to local escalation of privilege with System executioEPSS 0.1%CVE-2023-20618MEDIUMIn vcu, there is a possible memory corruption due to improper locking. This could lead to local escalation of privilege with System executioEPSS 0.1%CVE-2026-42489MEDIUMdomctl lock open to abuseEPSS 0.1%CVE-2023-21000HIGHIn MediaCodec.cpp, there is a possible use after free due to improper locking. This could lead to local escalation of privilege with no addiEPSS 0.1%CVE-2026-20757LOWImproper Locking vulnerability (CWE-667) in Gallagher Morpho integration allows a privileged operator to cause a limited denial-of-service iEPSS 0.1%CVE-2023-20737MEDIUMIn vcu, there is a possible use after free due to improper locking. This could lead to local escalation of privilege with System execution pEPSS 0.1%CVE-2023-20733MEDIUMIn vcu, there is a possible use after free due to improper locking. This could lead to local escalation of privilege with System execution pEPSS 0.1%CVE-2023-20745MEDIUMIn vcu, there is a possible out of bounds write due to improper locking. This could lead to local escalation of privilege with System executEPSS 0.1%CVE-2023-20743MEDIUMIn vcu, there is a possible out of bounds write due to improper locking. This could lead to local escalation of privilege with System executEPSS 0.1%CVE-2023-20746MEDIUMIn vcu, there is a possible out of bounds write due to improper locking. This could lead to local escalation of privilege with System executEPSS 0.1%CVE-2023-20939HIGHIn multiple functions of looper_backed_event_loop.cpp, there is a possible way to corrupt memory due to improper locking. This could lead toEPSS 0.1%