CVE-2026-19738 Retained RX node leak and reachable assertion in Bluetooth Controller CIS Create procedures

The Bluetooth Link Layer Control Procedure LLCP implementation for Connected Isochronous Stream CIS creation retains an RX node ctx-noderef.rx, marked NODERXTYPERETAIN so it can later be reused as the host notification — on the peripheral while awaiting the Host's reply to an LLCISREQ, and on the...

terraform-aws-secure-baseline

terraform-aws-secure-baseline Terraform Module Registry Un módulo de Terraform para configurar tu cuenta de AWS con una línea base de seguridad razonablemente segura. La mayoría de las configuraciones se basan en CIS Amazon Web Services Foundations v1.4.0 y AWS Foundational Security Best Practice...

dockle

Dockle - Linter de imágenes de contenedor para seguridad, ayudando a construir la imagen Docker de mejores prácticas, fácil de empezar Dockle te ayuda a: 1. Construir imágenes Docker de Mejores Prácticas 2. Construir imágenes Docker seguras Los puntos de control incluyen CIS Benchmarksbash $ brew...

docker-bench-security

Docker Bench for Security Docker Bench for Security es un script que verifica docenas de buenas prácticas comunes en torno al despliegue de contenedores Docker en producción. Todas las pruebas están automatizadas y se basan en el CIS Docker Benchmark v1.6.0. Lo ponemos a disposición como una...

csf

ArmourBird CSF - Marco de Seguridad para Contenedores Nota: El Cliente CSF está en desarrollo activo y se está convirtiendo a GoLang para un mejor rendimiento y arquitectura Tabla de Contenidos 1. Acerca de 2. Diagrama de Arquitectura 3. APIs del Servidor CSF 4. Instalación/Uso 5. Construcción de...

CVE-2026-19738: Missing Release of Memory after Effective Lifetime

The Bluetooth Link Layer Control Procedure LLCP implementation for Connected Isochronous Stream CIS creation retains an RX node ctx-noderef.rx, marked NODERXTYPERETAIN so it can later be reused as the host notification — on the peripheral while awaiting the Host's reply to an LLCISREQ, and on the...

windows_hardening

HardeningKitty e Windows Hardening Introduzione Il progetto è nato come una semplice lista di hardening per Windows 10. Dopo qualche tempo, è stato creato HardeningKitty per semplificare l'hardening di Windows. Ora, HardeningKitty supporta le linee guida di Microsoft, CIS Benchmarks, DoD STIG e B...

EUVD-2026-77629

The Zephyr SDIO subsystem function sdioiorwextendedhelper in subsys/sd/sdio.c finishes transfers with a byte-I/O loop that uses size = MINremaining, func-cis.maxblksize as the per-iteration step. The value func-cis.maxblksize is decoded directly from the SDIO card's CIS FUNCE tuple in sdiodecodec...

Evaluating and Preventing Security Smells in AI-Generated Ansible Code

AI coding assistants generate Infrastructure as Code, yet no work has examined whether this code meets security requirements. This matters because security smells in infrastructure code propagate to deployed systems, producing infrastructure that is insecure and untrustworthy. We evaluate 16 AI...

GO-2025-3955 vulnerabilities

Vulnerabilities for packages: bom, aws-otel-collector, opa, k3d, docker-machine-driver-harvester, ko, prometheus-operator, kube-logging-operator, mockgen, polaris, nri-apache, aws-privateca-issuer, rancher-system-upgrade-controller, grafana-alloy, ini-file, grafana-rollout-operator, rclone,...

TopoIntent: Compiling Security Intent into Executable, Compliance-Checked Network Topologies

Enterprise security topology design requires translating business intent, regulatory requirements, and risk assumptions into zones, boundary devices, inter-zone paths, and access-control policies. Existing NetOps automation tools mainly operate after this design is fixed, providing limited suppor...

Does Fixing Break Security? an Empirical Study of Security Degradation in Iterative LLM-Driven Infrastructure-As-Code Repair

Background: Iterative feedback loops are the dominant paradigm for improving LLM-generated Infrastructure-as-Code IaC: validators such as Checkov and terraform validate feed error signals back for successive repair attempts. Prior work reports cumulative-best metrics, which are non-decreasing by...

ad-hardening-pentest-lab-

Active Directory Hardening & Mutual Pentest Lab A self-contai...

kube-bench v0.16.0

kube-bench is a tool that checks whether Kubernetes is deployed securely by running the checks documented in the CIS Kubernetes Benchmark. Tests are configured with YAML files, making this tool easy to update as test specifications evolve. CIS Scanning as part of Trivy and the Trivy Operator Triv...

From Backlog Items to Security Guidance: Towards Continuous Security Compliance

Continuous software engineering in regulated domains requires engineering teams to address security throughout the development lifecycle. Yet making security requirements explicit in backlog items is still problematic. Engineers must instead infer security relevance of backlog items from brief,...

cis-hardening-metasploitable2

CIS Benchmark Hardening in Practice: A Full Attack-to-Remediat...

CVE-2026-63944

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hcisync: fix UAF in hcilecreatecissync hcilecreatecissync dereferences conn-conntimeout after releasing both rcureadlock and hcidevlockhdev. The conn pointer was obtained from an RCU-protected iteration over...

CVE-2026-63944 Bluetooth: hci_sync: fix UAF in hci_le_create_cis_sync

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hcisync: fix UAF in hcilecreatecissync hcilecreatecissync dereferences conn-conntimeout after releasing both rcureadlock and hcidevlockhdev. The conn pointer was obtained from an RCU-protected iteration over...

CVE-2026-63944

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hcisync: fix UAF in hcilecreatecissync hcilecreatecissync dereferences conn-conntimeout after releasing both rcureadlock and hcidevlockhdev. The conn pointer was obtained from an RCU-protected iteration over...

CVE-2026-63944

The set of CVE records (CVE-2026-63944) describes a Linux kernel issue in Bluetooth hci_sync: hci_le_create_cis_sync that can cause a use-after-free by dereferencing conn->conn_timeout after releasing rcu_read_lock() and hci_dev_lock(hdev). The conn pointer originates from an RCU-protected ite...