Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • BIND BIND
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 527
    • Issues 527
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 95
    • Merge requests 95
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source Projects
  • BINDBIND
  • Issues
  • #3400
Closed
Open
Created Jun 13, 2022 by Peter Davies@peterdDeveloper

uv_start_read() may get called with a closed tcp session

uv_start_read() may get called with a closed tcp session:

There may be a timing issue in BIND 9.18.? BIND could crash if a tcp connected was closed or reset in the time between the TCP connection is established and isc_nm_read() is called.

The callback tcp_connected() calls isc_nm_read() which schedules isc__nm_async_tcpdnsread() on the nmworker loop.
If the connection is closed in the meantime uv_start_read() is called in the next iteration of the loop

RT #20876

Assignee
Assign to
Time tracking